ChirplyA shared inbox has no clock
Email has no concept of due, owned or breached. The oldest unanswered message is discoverable only by scrolling, which means it is discoverable only by accident.
- SaaS & software businesses
- Agencies supporting client accounts
- Anyone with a support@ address
- Service businesses with SLAs
- Teams outgrowing a shared inbox
Support lives in a shared mailbox. So does everything you promised.
Tickets with queues, priorities, assignees and SLA timers, a branded public portal customers submit through, and a CSAT score collected when the ticket closes — on the same contact record that holds their invoices, their calls and every text you have exchanged.
Start 14 days free $0 today · no contract · cancel any time
- Unlimited contacts; provider usage billed separately
- Scale trial access; partner tiers are separate
$0charged today
14 daysfree, on the top plan
No contractcancel before day 14, never billed
Unlimitedcontacts on every plan
Nobody can tell you how long that customer has been waiting, because the answer is buried in a mailbox three people half-read.
What it is costing you
The problem is not that it is hard.
It is that nobody has the hours, and the cost of skipping it never shows up as a line on any invoice.
The customer has no idea whether you saw it
Without a status they can check, the only way for them to find out is to email again — which lands as a second thread, on a different day, in front of a different person.
Support is invisible to the rest of the business
The account manager cannot see the three angry tickets before the renewal call, because support history lives in a tool that has never met the contact record.
How it works
Set up once. It runs from then on.
- 1
Open
Give them a front door
A branded public portal where customers submit a ticket — no account, no login, no password to lose. Each ticket gets a secure status link they can follow to see where it stands.
- 2
Queue
Put a clock and an owner on it
Queues, priorities and assignees, with an SLA due time tracked per ticket, so 'who has this and when is it due' is a field rather than a conversation in standup.
- 3
Resolve
Work it beside everything else you know
The ticket sits with the contact's payments, appointments, calls and conversation history — so the person answering already knows what they bought and what happened last time.
- 4
Measure
Ask whether it was any good
On resolution the requester is asked for a CSAT score and a comment. What you learn is attached to the ticket, the agent and the customer, not to a survey tool nobody exports.
What you get
Every piece of this is already live.
These are not roadmap items. Each one is running in production today, described here in the same words the full product catalog uses.
Tenant help desk
Run your own support operation — tickets, SLAs and satisfaction scores — under your own brand.
Every workspace gets a help desk at /helpdesk: a branded public portal where customers submit tickets, agent queues with priorities and SLA timers, and a CSAT score collected when the ticket closes.
- Branded submission portal and a secure per-ticket status link — no login needed to follow a ticket
- Queues, priorities, assignees, and SLA due times tracked per ticket
- CSAT score and comment collected from the requester on resolution
- Replies land on the ticket's status link and notify your team by push — email delivery of replies isn't built yet, so requesters follow the link
Unified conversations inbox
Stop switching apps to find out what you already told them.
Inbound and outbound SMS, email, WhatsApp, Messenger, and Instagram threaded together per contact, with color-coded bubbles for direction.
- Reply from the inbox or straight from the contact record
- Inbound email routed in via your own sending domain
- WhatsApp, Messenger, and Instagram sit in the same thread as SMS and email
- Every message on the shared activity timeline
Live chat & AI handoff
Capture the question while the buyer is still on the page.
Embed a branded chat widget, answer from the Chirply inbox, let AI handle routine turns, and take over with the full visitor and conversation context intact.
- Multiple widgets with their own branding and status
- Shared human inbox with close and takeover controls
- AI-to-human and human-to-AI handoff
- Visitor identity and click-path context beside the conversation
Tasks & activity timeline
Nothing falls through, and you can prove what happened.
A tabbed activity feed on every contact with multi-select filters by channel and direction, plus tasks with priorities and due dates.
- Calls, SMS, email, AI sessions, payments, and automation runs on one timeline
- Filter to just inbound calls, or just email, in a click
- Tasks created by hand, by an automation, or by an AI agent taking a message
Contacts & companies
One record per human, with everything they've ever done on it.
Inline-editable contact records with companies, business name, website, and address — plus your own custom fields for whatever your business actually tracks.
- Custom fields of every type, usable as merge fields everywhere
- Phone matching that ignores formatting — (409) 893-0064 finds 4098930064
- Duplicate phone numbers are refused on the way in, and anything already doubled up is surfaced for you to sort out
- Tags, lifecycle stage, and per-row quick actions
Visual workflow builder
Build the follow-up once and let it run forever.
Multi-step workflows with waits and branching, triggered by what actually happens in your business.
- Triggers: contact created, tag added, deal stage changed, form submitted, message received, call completed, on a schedule, or manually / by webhook
- Steps: send SMS or email, add or remove tags, add to a list, move a pipeline stage, create a task, wait, call a webhook, notify your team
- Branches read your own custom fields as well as the built-in ones, and steps can fill a custom field from what the event carried
- Voice steps: ringless voicemail, outbound IVR, sales bridge, AI call, enroll in a campaign
This is the part of Chirply that solves help desk. See the other 14 areas — CRM, scheduling, messaging, automations, funnels, commerce, reputation and the rest — all included in the same workspace.
The offer
Try it on your own business for 14 days.
You do not have to migrate anything to find out whether this works. Start the trial, set up the one thing you came here for, and judge it on that.
- $0 charged today. A card holds the workspace; nothing moves until day 14.
- Unlimited contacts. Communication channels depend on your plan; calls, messages and AI are billed by your providers.
- Your providers, your rates. Bring your own Twilio, Mailgun and AI keys and pay them directly — we do not mark usage up.
- No contract. Cancel before day 14 and you are never billed.
Your trial runs on Scale, the top plan, so nothing is locked while you evaluate. If help desk is all you need afterwards, Grow at $77/mo carries it — switch down before the trial ends and keep the lower price.
Your order
Start free for 14 days.
$0 today. A card keeps the workspace running after the trial, and Scale renews at $97/month unless you change plans or cancel first.
- Scale plan — 14-day trialThe whole platform, nothing locked
- $0
- From day 14, unless you switch or cancelChange plans or cancel any time before then
- $97/mo
- Due today
- $0.00
Cancel any time before day 14 and nothing is charged. Calls, texts, emails and contacts are unlimited on every plan — you bring your own Twilio, Mailgun and model keys and pay those providers directly.
No trial subscription charge today. Cancel before renewal.
Provider usage and optional app purchases are separate. The card only exists so a workspace you decide to keep does not stop working on day 31.
Before you start
The questions everyone asks.
Which plan includes the help desk?
Grow, at $77 a month, and Scale above it. It is a full workspace capability, not a per-agent seat charge — ten seats on Grow and unlimited on Scale, all working the same queues.
Does it email replies to the customer?
Not yet, and it matters enough to say plainly: replies land on the ticket's status link and notify your team by push, but email delivery of replies is not built. Requesters follow their secure status link to read what you wrote. If threaded email replies are non-negotiable for you, wait for that to ship.
Do customers need an account?
No. They submit through the branded portal and follow a secure per-ticket status link. Nothing to sign up for, nothing to remember, and no support ticket about the support portal.
How is this different from the shared inbox you already have?
The unified inbox is for conversations — texts, email, WhatsApp, Messenger and Instagram DMs threaded per contact. The help desk is for obligations: an owner, a priority, a due time and a resolution. Most teams end up running both, on the same contact record.
Can support work start automations?
Yes. Because tickets sit on the CRM, workflows can create the follow-up task, tag the account, notify a manager, or text the customer — and a live chat conversation can be handed from AI to a human with the visitor's context intact.
Weighing it against something specific?