Sonaris for SaaS software companies
A shared support inbox with SLAs, a pipeline from trial to signed, a help centre published from a folio and onboarding projects your customers can see. The product stays yours; everything around it runs on one workspace.
- One support inbox the whole team shares1 / 14Messages
- Accounts, tickets and a sales pipeline2 / 14CRM
- A help centre and a site that books demos5 / 14FolioSitesForms
- Roadmap, onboarding and automation11 / 14FlowsProjectsChatCanvasChecklistsProfiles
An illustrative workspace. The business, people and figures are fictional.
One support inbox the whole team shares
support@ and sales@ become shared inboxes. Every thread has an owner and a read state, the team talks in internal notes beside the customer's message, and a thread can be transferred, assigned or closed without forwarding anything.
- Shared inboxes per team or purpose
- Internal notes alongside the thread
- Transfer, assign and close
- Every conversation filed on the contact
Accounts, tickets and a sales pipeline
Contacts map to the company they work for, so a ticket from one manager shows the whole account. Tickets carry SLAs, deals move from trial to signed, and segments drive product-update newsletters. Your old CRM comes in from CSV.
- Relationship mapping between people and companies
- Tickets with SLAs and automations
- Deals and pipelines with stage automations
- Segments, newsletters and campaigns
Trial
Demo
Won
A help centre and a site that books demos
Help articles and the changelog are a folio published under a path on the marketing site, with its own search. The demo-request form creates a contact and a deal, and a booking page lets them pick the slot themselves.
- A folio published to the site, with its own search
- Visual editor, plus a code editor for template pages
- Forms that create a contact and a deal
- Booking pages for demos
Staff can offer a shift from the app. A manager approves it, and the rota updates for both people.
Swaps not showing?
Check that both people are on the same site and that the shift is more than two hours away.
Roadmap, onboarding and the glue between them
The roadmap and bug board are projects, feature maps live on a canvas, and the team talks in channels. Larger customers get an onboarding project and room with their admins as guests. Flows provisions the account over HTTP when a deal is won, escalates tickets near their SLA and follows up quiet trials.
- Projects with board, list and timeline views
- Channels, DMs and project rooms with guests
- Onboarding checklists attached to the customer's project
- Call out over HTTP to your own product
- Trigger · CRMDeal wonwhen
- Action · HTTPProvision the account in Ostra Rotathen
- Action · ProjectsCreate project from “Group rollout”then
- Action · ChecklistsAssign “Enterprise onboarding”then
- Action · ChatInvite the customer's admin as a guestthen
- Trigger · CRMTicket unanswered for 2 hourswhen
- ConditionAccount has more than 10 sitesif
- Action · MessagesAssign to the on-call engineerthen
- Action · ChatPost to #support-escalationsthen
- Trigger · CRMContact went quiet for 7 dayswhen
- ConditionDeal is in the Trial stageif
- Action · MessagesDraft a check-in from sales@then
- Action · CRMMove deal to “Nurture”then
Support, sales and product looking at the same customer
A support thread shows the account's deal, its onboarding project, the help article it needs and the bug it is waiting on. Sales, support and engineering stop asking each other what the customer said.
- FormsDemo request: Fiore Kitchens, 6 sites
- MessagesSwap sync thread answered in 48 min
- Folio4.12 changelog published
- CRMHarbourside Hotels · won
- Flows22 sites provisioned over HTTP
- ChatHarbourside admin joins their room
- CRMProduct update to 1,900 users
- Seats
- 18 · support, sales, product and engineering
- Guests
- Customer admins during onboarding
- Billing
- Subscriptions stay in your own billing system; Flows can reach it over HTTP
- Replaces
- Zendesk, Help Scout, HubSpot, Notion, Webflow, Typeform, Slack, Asana, Miro and Zapier
Start with one module. Add the rest as you grow.
Every module works with every other from the day you switch it on, and your data exports whenever you want.