Install AskVault in Intercom
What this integration does
Two patterns:
- AskVault as the primary bot. Bot reads incoming Intercom conversations, drafts answers, sends via the Intercom Conversations API. Resolves in-conversation or hands off to humans.
- AskVault augments Intercom Fin. Both bots run; AskVault handles your knowledge-base queries, Fin handles the rest. Customer sees one bot UX.
Pick the pattern at setup. Most teams use AskVault as primary.
Why pair with Intercom
Three reasons:
- Existing investment. Your team already lives in Intercom. AskVault augments rather than replaces.
- Resolution rate. AskVault's source-cited answers handle questions Intercom's flow-builder bots can't.
- Cost. AskVault on top of Intercom Foundation tier is cheaper than upgrading to Intercom Pro for advanced bot features.
Setup walkthrough
About 20 minutes:
Step 1: connect via OAuth
- Open Deploy Hub > Intercom > Connect.
- Click "Sign in with Intercom".
- Pick the Intercom workspace.
- Approve scopes:
- Read conversations.
- Write conversations (post replies).
- Read contacts.
- Read teams (for routing).
Setup time: about 2 minutes.
Step 2: configure routing
- Open Intercom > Operator > Bots.
- Add the AskVault bot to the bot flow.
- Pick where it fires: before Intercom Fin, after, or as a standalone.
- Configure trigger conditions:
- Customer tag matches X.
- Inbox is X.
- Time of day.
- Conversation reopen events.
Step 3: map handoff teams
When AskVault can't resolve and escalates, it transfers to a specific Intercom team:
- Open Intercom > Settings > Teams.
- Note team IDs.
- In AskVault: Deploy Hub > Intercom > Routing. Map skill outcomes to Intercom teams (e.g., refund-related → Billing team).
Step 4: test
- Send a test message from a test contact in Intercom.
- AskVault replies within 5 seconds.
- Reply triggers Intercom event which AskVault receives.
Confirm the conversation flows correctly.
Permissions and scopes
What AskVault reads from Intercom:
- Conversations. Messages, status, assignee.
- Contacts. Email, name, custom attributes, audience tags.
- Teams. For routing decisions.
- Tags. Applied tags on conversations.
What AskVault writes:
- Conversation replies.
- Internal notes (for context handoff to human agents).
- Tags.
- Assignments (to specific teams).
- Status changes (resolve, snooze).
Minimum-permission principle applied.
Bidirectional reply sync
How replies flow:
Customer message arrives in Intercom.
- Intercom posts webhook to AskVault within 30 seconds.
- AskVault analyzes: is this a knowledge question? Should the bot answer or pass to a human?
- If bot: AskVault replies via Intercom's API. Reply appears in the Intercom conversation thread.
- If human: AskVault sets the assignee and adds an internal note with context.
Human agent replies in Intercom.
- Intercom posts webhook to AskVault.
- AskVault records the reply in its conversation history for analytics.
- No further action; the human handles it.
Customer experience: one continuous conversation in Intercom.
Conversation status sync
Resolution:
- AskVault resolves → Intercom marks "closed".
- Intercom marks closed → AskVault marks resolved.
Snooze:
- AskVault snoozes → Intercom snoozes with same wake time.
- Intercom snoozes → AskVault snoozes.
Tags and priority sync bidirectionally too.
Intercom-specific skills
Some AskVault skills behave differently on Intercom:
ticketing_router. Doesn't create a new ticket since Intercom is the ticket system. Instead, routes the existing conversation to the right Intercom team.escalate_to_human. Assigns to a specific Intercom team or admin based on rules.collect_lead. Updates the Intercom contact rather than creating a new record.
Configure per-skill behavior under AI Agents > Skills > [skill] > Intercom.
Article suggestions
When AskVault knows a related Intercom Help Center article exists:
- Includes article links in bot replies.
- Helps the visitor self-serve before involving an agent.
Requires indexing your Intercom Help Center via Intercom integration setup.
Sample workflow
End-to-end:
- Visitor messages from your website widget (Intercom Messenger).
- AskVault receives webhook within 30 seconds.
- AskVault answers from your indexed knowledge. Reply appears in Intercom within 5 seconds.
- Visitor says "I need to cancel."
- AskVault's
subscription_managerskill verifies identity by checking Intercom contact attributes. - Bot answers with subscription details and offers to cancel.
- Visitor confirms.
- Bot processes via Stripe API; updates Intercom conversation; marks resolved.
Total time: about 2 minutes. Without AskVault: about 10 to 15 minutes of agent time.
Multi-workspace Intercom
For teams using multiple Intercom workspaces:
- Connect each separately to a different AskVault workspace.
- Or connect multiple Intercom workspaces to one AskVault workspace (Enterprise).
Configure under Integrations > Intercom > Instances.
Conversation deflection metrics
Track what AskVault deflected vs what reached humans:
- Bot-resolved. Conversations AskVault closed without human involvement.
- Bot-escalated. Conversations AskVault couldn't resolve; routed to a team.
- Hybrid. Bot answered, then a human took over later.
Visible under Analytics > Channel: Intercom.
Typical bot-resolution rate: 30 to 60% depending on knowledge coverage.
Audit and compliance
Every Intercom-routed action logs:
- Bot decisions with reasoning.
- Replies sent.
- Status changes.
- Team assignments.
Retained 365 days standard, 6 years Enterprise. Useful for compliance audits.
Plan availability
- Free, Starter. No Intercom integration.
- Growth. Basic bot replies plus routing. Growth+
- Business. Adds article suggestions, multi-workspace, advanced routing. Business+
- Enterprise. Custom skill behavior, dedicated infra.
Cost considerations
Side-by-side:
- AskVault subscription. ₹2,499 to ₹8,499 per month for Starter to Business.
- Intercom Foundation. About $39 per seat per month.
- Intercom Pro or Advanced. $99 plus per seat per month (for advanced bot features).
Pattern that often wins: Intercom Foundation plus AskVault. Cheaper than Intercom Pro for similar bot capability.
Planned features (on the roadmap)
Documented for accuracy:
- Custom message types. Today, text messages. Rich-card and inline-form support planned.
- Intercom Workflows v2 integration. Today, basic bot routing. Native Workflows integration planned.
- Cross-tenant conversation merge. Today, per-workspace. Multi-workspace conversation unification planned.
Limits
- Conversations per second. About 100 (Intercom API rate limit).
- Workspaces per integration. 1 (Growth), 5 (Business), unlimited (Enterprise).
- Reply latency. Under 5 seconds typical.
- Article suggestions per reply. Up to 3.
Common pitfalls
Bot doesn't reply to some conversations. Trigger conditions too narrow. Audit under Intercom > Operator > Bots.
Replies post twice. AskVault and Intercom Fin both replying. Either disable Fin or order them properly.
Status sync drift. Webhook subscription incomplete. Re-subscribe under Integrations > Intercom > Webhooks.
Article suggestions don't appear. Help Center not indexed. Run Intercom knowledge ingestion.
FAQ
Does AskVault replace Intercom?
No. Augments. Your team continues using Intercom; AskVault handles bot-resolvable questions.
Will the bot interfere with Intercom Fin?
Only if both fire on the same conversation. Configure them sequentially (AskVault first, Fin if AskVault doesn't resolve).
Can I use Intercom's contact data for personalization?
Yes. Identity verification reads Intercom contact attributes (plan, custom fields, tags).
Will AskVault create new Intercom conversations?
For inbound messages, yes (reply in-thread). For outbound proactive messages, configure under Deploy Hub > Intercom > Outbound.
Does this work with Intercom on mobile (in-app)?
Yes. The Intercom Messenger SDK on mobile receives AskVault replies the same way as web.
Related guides
- Intercom integration setup
- Compare to Intercom Fin
- Identity verification
- Skills overview
- Escalate to human skill