Your support desk resolves tickets, not just routes them. Connect Freshdesk, Intercom, and Slack, and a ModuleX agent reads each ticket, drafts the reply with the customer’s history in hand, and escalates the real bugs to engineering.
FreshdeskA ticket arrivesget_ticket- ModuleX agentRead and classify
- FreshdeskPrioritize and route
set_ticket_priorityassign_ticket_to_agent 
SlackNotify #supportpost_message
Triage lands before a human opens the queue. The agent sets priority and posts to Slack.
A ModuleX agent reads new Freshdesk tickets, sets a priority, assigns the right agent, tags the ticket, and posts a short summary to your support channel in Slack, so nothing sits in an unread queue waiting to be noticed.
- Freshdeskcreate_ticket · get_ticket
- Slacklist_channels · post_message
Replies start as drafts, not blank boxes. The agent grounds them in the customer’s own history.
For an open Intercom conversation, the agent pulls the thread, reads the contact’s history and tags, and drafts a reply that already knows what was said. It lands as a note for a teammate to review and send, and the agent can tag the contact so the next message routes itself.
Intercomget_contact · search_contacts
A bug becomes a tracked issue, not a lost thread. Engineering gets it with context.
When a ticket turns out to be a bug, the agent opens a Linear issue, or a GitHub issue, with the customer details and a summary of the conversation attached, so engineering picks it up with the context already there.
Linearget_teams · get_issue
GitHublist_repositories · create_repository
Paste a request. Watch it resolve. Each one runs an end-to-end recipe you can open.
“When a new Freshdesk ticket comes in, set its priority, assign it to the right agent, and post a short summary to our #support channel in Slack.”
See the recipe“Read the latest Intercom conversation, draft a reply grounded in the thread and the customer’s history, and leave it as an internal note for an agent to review.”
See the recipe“Tag every unassigned Freshdesk ticket about billing, raise its priority, and let the on-call agent know in Slack.”
See the recipeRecipes for customer support teams. Open one for the steps, the prompt, and the apps involved.
Support Ticket TriageNew tickets get read, prioritized, and routed the moment they land, and the urgent ones surface in Slack instead of sitting in a queue. A ModuleX agent classifies each Freshdesk ticket, sets its priority and tags, assigns it, and posts the ones that cannot wait.6 steps · on every new ticketGrounded Support RepliesEvery reply starts as a grounded draft that already knows the customer’s history, so agents edit instead of writing from scratch. A ModuleX agent reads the Intercom conversation and contact, drafts a reply, and leaves it as a note for a human to approve.6 steps · on demand
Answer an order question with the order in handA reply that answers with the real order status instead of asking the customer for their order number. Built for an ecommerce team answering the same three questions about where a package is.5 steps · on every new recordAnswer support questions using your own documentationA drafted answer grounded in your own material, showing what it drew from, behind an approval step. Built for support teams whose answers already exist, just not where the question arrives.4 steps · on demand
See which accounts went quiet this weekOne weekly digest naming the accounts that have gone quiet, with what each signal was. Built for a customer success manager who finds out about churn after it happens.5 steps · weeklyTurn a customer email into a tracked issueA tracked issue an engineer can pick up without opening the email, and a customer who knows it was logged. Built for support and product teams where bug reports die in an inbox.5 steps · on demandTriage the support queue before your shift startsA queue that is grouped and ordered, with repeated issues visible as one cluster. Built for a support lead who opens the queue to sixty tickets and no order to them.4 steps · on every new ticketEverything this team already runs on. Connect once and your agents can act across all of it.
Teammates run it. You keep the keys. Credentials live in the org vault and every run lands in the audit ledger.
See the credential vaultModuleX for customer support FAQ
Your organization's own. You connect Freshdesk, Intercom, Slack, and the rest once, and the keys are encrypted in the org credential vault. Teammates run workflows without ever seeing a key.