Support that protects revenue.
Deskline puts the customer's plan, payment health and subscription controls inside the conversation, so your team can rescue a failed payment or stop a cancellation while they are still talking to the customer.
What you are probably doing today
A shared WhatsApp number in one tab, the billing dashboard in another, and an agent copying a ticket number between them. The customer waits, the 24-hour window closes, and a failed payment quietly turns into churn.
Deskline closes that loop. The conversation, the plan and the payment controls are the same screen.
Why it is different
Act on the subscription, inside the ticket
Payment health, plan, renewal date and open invoices load with the conversation. Cancel at period end, pause, resume or send a payment-portal link without opening Stripe in another tab.
WhatsApp, handled the way WhatsApp works
The 24-hour service window is tracked per conversation with a live counter, and template selection is forced once it closes. Approved templates are managed from the desk, and each message's cost is recorded separately from your subscription.
The account, not just the ticket
Contacts resolve by phone number, email or billing id, normalized for Mexican and Argentine dialing quirks. Accounts carry one timeline of messages, plan changes and payments.
One desk for every product you support
Each product gets its own widget key, forms, team, SLA and intake tree inside a single workspace, so a growing portfolio does not become a second subscription or a second login.
How it works
Connect a channel
Choose a regional pack and Deskline seeds categories, macros, routing rules and a help center. You get a support inbox address right away; connect a WhatsApp line or paste the widget snippet when you are ready.
Let it triage and route
AI classifies category, priority and sentiment on arrival. Assignment rules send the ticket to the right team by product, module or keyword, and the SLA clock starts on your business hours.
Answer with the whole picture
The agent sees the plan, payment health and past tickets, gets a suggested reply grounded in your own articles, and can act on the subscription without leaving the thread.
Embedding is one line
WhatsApp and email need no code at all. Putting support inside your own product is a single script tag, with a signed identity handoff when you want verified users.
<script src="https://your-deskline.app/api/public/widget.js"
data-deskline-key="wk_live_xxxxxxxx" async></script>What is working today
An honest inventory. Anything still unbuilt is marked as roadmap rather than described as a feature.
Channels
- WhatsApp Business with service-window and template handling
- Email to ticket, with threading and deduplication
- Embeddable widget with signed identity handoff
- Public ticket forms and lead capture forms
- Customer portal that needs no account
- A public help center per workspace
The desk
- Assignment rules, round-robin and teams as queues
- SLA policies on your business hours, applied on arrival
- Macros, bulk actions and a configurable inbox grid
- Product, module and category intake taxonomy
- CSAT sent automatically when a ticket resolves
- Roles, permissions and per-ticket access rules
Revenue
- Stripe sync of subscriptions, invoices and disputes
- Payment health, past-due and pending-cancellation flags
- Cancel, pause, resume and payment-portal links from the ticket
- Churn-risk marking and a win-back opportunity on cancellation
AI
- Triage of category, priority and sentiment on arrival
- Suggested replies grounded in your own articles
- Thread summaries for handoffs
- Cost tracked per workspace, with soft and hard monthly caps
Compared with the setup you already have
This is not a feature-count contest against Zendesk. These are the four things that change day to day.
| Situation | Shared number and a billing tab | With Deskline |
|---|---|---|
| A customer's card just failed | Look them up in the billing dashboard, copy the payment link, paste it back into the chat | Payment health is already on the ticket, and the payment-portal link is one click |
| The 24-hour WhatsApp window is about to close | Nobody notices until the free-text reply is rejected | A live counter on the thread, and template selection is forced once it closes |
| You need to know what WhatsApp cost this month | Read Meta's invoice and guess which conversations it covers | Each message's cost is recorded per conversation, separate from the subscription |
| Your team works in Spanish | An English console with a partial translation layer | Spanish and English throughout, with parity enforced in the test suite |
How pricing will work
Deskline is in beta and does not charge yet, so there is no price list to publish. Rather than invent one, here is exactly what the product already meters — the basis any future plan will use.
Per agent seat
The desk, one product, and every channel that needs no code. Members and roles are already tracked per workspace.
WhatsApp at cost
Meta's per-conversation charge is recorded message by message and shown on its own, so it is passed through rather than marked up.
AI on a metered allowance
Every AI call already records its tokens and cost, and each workspace can set a soft and a hard monthly cap.
Straight answers
- Is this ready for production?
- It is in beta. The desk, routing, SLA, the channels listed above and the Stripe integration are wired end to end and covered by an automated test suite. Retention reporting and the rescue playbooks are not built yet, so treat the roadmap items as roadmap.
- Can I move off Zendesk or Freshdesk?
- Not in one click — there is no import tool yet. You can run Deskline alongside your current desk for one product or one channel, which is how we would suggest starting in any case.
- Do you have live chat or phone channels?
- No. WhatsApp, email, the widget, forms and the portal are the channels that work today. If live chat is your main requirement, Intercom or Crisp will serve you better right now.
- What if I do not use Stripe?
- The billing layer sits behind a provider interface and Stripe is the adapter that is live. Mercado Pago is planned behind the same interface. With no billing provider connected Deskline still works as a desk — you just lose the revenue context that makes it different.
- Where does my data live, and who can see it?
- Every table carries a workspace id and enforces Postgres row-level security, and agent access narrows further to the tickets their role and team allow. There is no SOC 2 report and no signed DPA yet; if procurement requires those, we are not the right fit today.
- What does it cost?
- Nothing yet, and there is no published price list. The pricing section above shows the basis the product already meters.