Answer support questions using your own documentation
A 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.
Gmail
4 steps1 integrationRuns on demand
The answer exists, just not where the question arrives. What it costs while the work is still done by hand.
- 01The answer is in your docs, and nobody can find it mid-shift.
- 02Two teammates answer the same question two different ways.
- 03A one-minute reply takes ten minutes of searching.
- New questionshared inbox · SSO setup
- Retrieve docs4 passages · 2 sources
- Draft replygrounded · sources listed
- Approve sendsend_message · sent
One workflow, four steps. ModuleX drafts this graph from a single sentence, and every step stays editable.
- 01A question arrives in a shared inbox or channel.Gmail
- 02Retrieve the relevant material from your knowledge base.ModuleX
- 03Draft a reply from what was retrieved, with its sources.ModuleX
- 04Review and approve before it sends.Gmail
The workflow is an editable graph. Reading runs freely; review and approve before it sends waits for your opt-in approval until you loosen it. The graph is the receipt.
Answers from your own docs. Paste this into ModuleX chat, or hit Use this workflow.
answer support questions using your own documentation: a question arrives in a shared inbox or channel; retrieve the relevant material from your knowledge base; draft a reply from what was retrieved, with its sources; review and approve before it sends. Ask me before anything is sent or written.
to: composerOr skip the workflow entirely. Ask the assistant in chat and it runs the same job agentically: it picks the right actions, chains them, and reports back. The composer is for when you want it repeatable.
Answer support questions using your own documentation. A drafted answer grounded in your own material, showing what it drew from, behind an approval step.
- gmail · send_message
A drafted answer grounded in your own material, showing what it drew from, behind an approval step.
Where this fits. The tools it runs on, and the teams that run it.
Keep the momentum. Nearby workflows that reuse the accounts you just connected.
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.
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.
Turn 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.
About this use case.
No. It answers from the knowledge base you connect. You choose the store: ModuleX-managed, or your own Qdrant, Pinecone, MongoDB Atlas or Weaviate.