CRM, support inbox, marketing, knowledge base, billing and AI agents in one role-based workspace. Built for operator teams that run all of it with 5 to 30 people.
Live demo on your own data · 30 minutes · No setup
A CRM, a help desk, a docs tool and an automation tool means four subscriptions, four permission models and four places the answer might be. Xappex keeps the ticket, the contact, the subscription and the article on one record.
Contacts, companies, tickets, chats, emails, subscriptions, invoices and articles share the same object graph.
Every suggested reply and chatbot answer is retrieved from your own records and docs, and shows where it came from.
Profiles, roles and field-level access. Switch marketing or billing off for a whole team and it disappears everywhere.
Automation steps read and write CRM records directly. Nothing to authenticate, no webhook to babysit.
Turn a pillar off for a team that doesn't need it. Everyone who has it on works on the same data.
Contacts, companies, activities and tasks out of the box. Custom objects, custom fields, formulas and validation rules when your business isn't.
Gmail inboxes and the chat widget land in one queue, threaded to the contact, with the subscription one glance away.
Build audiences from any filter or CSV, write once in the emails library, send on a schedule or from an agent.
Every article is tagged internal or customer-facing. The help center shows one set, your team sees both.
Chargebee subscriptions, plans and invoices mirror into the CRM and stay in sync through webhooks.
A visual builder with triggers from tickets, chats, forms, emails and schedules. Steps read and write CRM data directly.
Every answer in the inbox, in the chatbot or inside an agent run is retrieved from your own records and articles. Actions that matter wait for a human.
Most tools make you pick between a public help center and an internal wiki. Xappex tags every article by audience. The help center and the customer chatbot only see customer articles. Your team, and the AI drafting their replies, see everything.
Xappex borrows the parts of enterprise CRM that operator teams actually need, and leaves the consultants at home.
Object, field and record-level access. Sharing rules and groups for the exceptions. A billing-only profile sees invoices and nothing else.
Marketing, billing, support and docs can each be switched off for a whole team. Disabled pillars leave navigation, search and the API.
Who changed what, when, from where. Every record carries its history tab. Deletes go to a recycle bin first.
Scoped API tokens with rate limits, idempotency keys on writes, and an outbound events bus so your other systems hear about changes.
CAN-SPAM, CASL and GDPR unsubscribe handling, bounce suppression and opt-out imports are on by default.
Each organization is a separate tenant with its own data, roles and pillars. HTTPS everywhere.
Native connections, not recipes. Syncs are resumable, incremental and logged.
Multiple inboxes into one queue. Threaded replies, inline images, automated-sender detection.
Import contacts, companies, tickets and segments. Incremental after the first pass.
Subscriptions, plans and invoices mirrored. Seat writes through one audited path.
Notifications, chat handoff threads, approve agent actions without leaving Slack.
Marketing and transactional sending. Bounce and unsubscribe webhooks handled.
Bank feed for invoice reconciliation, with learned counterparty aliases.
Also: an embeddable chat widget and forms with a JS API, website visitor tracking, CSV import and export for every object, OpenAI or any compatible provider, and a REST API with webhooks.
You will want to when if you start using Xappex. Having one source of truth across Marketing, Billing, and Support accessible over MCP and API is incredibly powerful. But no rush, many teams start with the support pillar and documentation. HubSpot or other CRM connection is available, so you can bring your data from anywhere. Turn on the other pillars when you're ready.
From your own records and articles. Suggested replies, chatbot answers and agent decisions retrieve from what you've stored in Xappex and cite the sources they used. Nothing is answered from general knowledge alone.
Only the ones you allow. An agent can draft, classify and route freely. Anything with a customer-facing or billing effect is held as a proposed action until someone approves it from Slack, email or the app.
The built-in provider by default. You can bring your own OpenAI-compatible endpoint and keys, set budgets per workspace, and see usage in the admin area.
Request a demo below. Bring a HubSpot export or a CSV and we'll import it live, connect an inbox and show you the first grounded reply on a real ticket. It takes about 30 minutes.
Bring a HubSpot export or a CSV. We'll import it live, connect an inbox, and show you the first grounded reply on a real ticket.
Already a customer? Sign in
