WhatsApp and API chat
Connect WhatsApp, or build chat into your app with the authenticated API. Each channel keeps its own customer identity and conversation history.
AI support for WhatsApp and your app.
Answer from your knowledge, use the tools you configure, and hand conversations to your team. Manage conversations and tickets in one project workspace.
S
loading example…
Available connections
configured for your project
configured for your project
Conversations
Outbound notificationsWhy teams switch
Support tools weren't built to take action.
Most teams are stuck between legacy ticketing and bolt-on assistants that never close the loop. Subport closes it.
More headcount, same backlog
Hiring doesn't move the queue if the queue grows linearly with headcount. Subport puts automation where it deflects, resolves, and hands off cleanly.
AI that stops at a draft
Copilots suggest text. Customers still wait. Subport connects replies to permitted tools, tickets and human handoff.
Weeks to wire channels and playbooks
Connect WhatsApp or your app, attach knowledge, and configure how work reaches your team.
The platform
Conversations, knowledge, and follow-up.
Illustrative product views with sample data. Configure agents and permitted tools around your team’s support process.
Sara Chen2m
How do I invite a colleague?
agent
Marcus Lee8m
WhatsApp · device pairing question
human
@miradev12m
API chat · export question
agent
Mira Rao18m
API chat · workspace question
agent
+91 98765…34m
WhatsApp · package delayed 4d
agent
Aria Patel1h
Workspace owner change request
agent
Search knowledge(question)
Find relevant content in linked knowledge bases
Create ticket(request)
Record a request using your ticket definition
Request handoff(context)
Bring a teammate into the conversation
Customer-data endpoint(configured inputs)
Use an enabled endpoint with identity and permissions
Approved MCP tool(declared inputs)
Use tools from an approved, linked server
WhatsApp
Authenticated API chat
Each channel keeps its own identity and thread. Additional channels are on the roadmap.
Search tickets, knowledge, navigate…esc
Tickets
Invite a colleague⏎
Workspace access request
Knowledge
Invite workspace members
Workspace roles
Navigate
Go to Team
↑↓ navigate·⏎ openSubport
Ticket volume · example120sample data
Support46%
Account29%
Billing18%
Other7%
The conviction
Built for the people running support — and the people building it.
Configure agents, knowledge and routing in your project. Extend with APIs and approved tools when your workflow needs them.
01
Operators configure the workflow.
Connect a supported channel, attach a knowledge base and choose the tools an agent may use.
02
Engineers don't hit a wall.
APIs, webhooks, custom tools, and workflows that match how your org actually resolves work—not a toy canvas.
03
Seats for people. AI that scales with the plan.
Review workspace prices and catalog allowances on the pricing page. Provider setup and usage depend on the integrations you configure.
What teams optimize for
Four things we hold automation to.
Speed where it's safe. Grounding everywhere. Gates where it isn't safe. These are the outcomes we design for, not measured results.
Resolved
Tier-1 without humans
where playbook + KB allow
Configured
Your support process
channels, knowledge and tools
Grounded
Knowledge-backed replies
citations from your sources
Gated
Destructive actions
human approval when you say so
Illustrative workflow
An answer first. A clear handoff when needed.
A product example, not a customer testimonial or measured result.
A customer asks about a return policy. The agent finds the relevant knowledge article. If the customer needs a teammate to review an exception, the conversation can become a ticket and a human handoff.
Order lookups require an endpoint or approved tool that your team configures. Actions depend on the available tools, customer identity and permissions; this example does not imply a built-in store or payment connector.
Explore agent capabilities →Available today
What you can configure now.
Knowledge and agents
Give agents your knowledge sources, model settings and permitted tools. Review conversations and hand work to your support team.
Tickets and workflows
Track work with ticket definitions, status, assignment and SLA policies. Configure Flows, webhooks and scheduled triggers for your process.
Connections you configure
Use customer-data HTTPS endpoints and approved MCP tools, including database tools exposed by your MCP server. Send outbound Slack notifications.
Roadmap
Planned channels and integrations.
Planned — not available today. These are product directions, not delivery commitments. Scope and availability may change; no release dates are promised.
Planned
Additional conversation channels
- Inbound email
- Voice and SMS
- Social messaging, including Instagram and X
- Inbound Slack and Microsoft Teams
Planned
Native business-system connectors
- Zendesk and Intercom
- Salesforce and HubSpot
- Shopify and commerce systems
- Zapier and calendar integrations
- Native database setup and visual query tools
Planned
Enterprise identity
- SAML and OIDC single sign-on
- SCIM provisioning
WhatsApp, authenticated API chat, outbound Slack notifications and configured MCP tools are described in our current platform overview.
Pricing
Per workspace, with AI work bundled in.
Compare workspace prices and catalog allowances for members, connected channels, AI agents and AI resolves. An AI resolve is a ticket closed by an agent without human intervention.
Starter
$39.20/workspace/mo · billed $470.40 yearly, or $49 monthly
Small teams getting serious about support.
- 3 configured AI agents
- 500 AI resolves / month
- Up to 10 team members
Pro
Pro
$119.20/workspace/mo · billed $1430.40 yearly, or $149 monthly
More catalog capacity for your support workspace.
- Unlimited team members and AI agents
- 3,000 AI resolves / month
- SLA policies, routing, knowledge base
Enterprise
Customdiscuss requirements
Discuss your volume, workflow and procurement requirements.
- Review your requirements
- Discuss available capabilities
- Confirm scope with our team
Connected channel allowances apply to supported channels. Planned integrations are not included as available features.
Too many “AI help desks” stop at text generation. The hard part is safe action: tools, approvals, audit trails, and a workspace for WhatsApp and authenticated API chat conversations.
That's what we're building—one place for support to run, with automation that earns trust.
If you have a sharp edge case, bring it. We'd rather lose a deal than sell a story we can't ship.
From the blog
Notes from the build.
Product controls
Access and action, with boundaries.
Project access, tool permissions and human review for support work.
Project access
Workspace groups and project permissions determine which resources a person can use.
Permitted tools
Agent tools are filtered by scope, identity and permissions. Sensitive operations can require confirmation.
Customer-data boundaries
Configured endpoints declare their identity bindings and response fields. Credentials are kept separate from model input.
Human review
Teams can review conversation history, ticket activity and approval requests.
FAQ
Before you roll it out.
Yes. Open the dashboard to get started, review the current plans on the pricing page, or request a guided demo.