Helpdesk, live chat and help centre
One inbox for email and live chat, and a help centre your customers can search. Every reply sits beside the person's orders, deals and past tickets, so nobody asks for an order number twice.
Hi, I ordered three days ago and haven't had a dispatch email. Is it on its way?
Hi Anna, your order left our warehouse yesterday and is due tomorrow before 1pm. Here's your tracking link.
Courier had delays in the North West yesterday. Worth a line if she's there.
Running their teams on Landing
What it replaces.
The helpdesk, the chat widget and the help centre, plus the tab you open to look up an order. Your support team works from one screen.
Tickets, macros and a help centre.
Tickets next to Shopify orders.
The chat widget and bots.
Customer emails nobody owns.
Everything the support team needs, and the context it never had.
The helpdesk you expect, on the same record as marketing, sales and orders.
One inbox
Email and chat in one queue, assigned by rule, with every conversation owned and timed.
Core and upLive chat and an AI assistant
A chat widget on your site and store, plus Messenger and Instagram messages and comments. The AI assistant answers from your help centre, citing the articles, shows products from your catalogue, and hands over to a person when asked.
Core and upA help centre
Articles your customers can search, on your own domain. Run a public centre, a client-only one behind their portal login and an internal one for the team.
Core and upReplies that know the customer
Orders, deals, bookings and past tickets beside every conversation, so the first answer is the right one.
Core and upSLAs and routing
First-reply and resolution targets by queue and customer, with breaches flagged before they happen.
Growth and upSuggested replies and AI agents
Drafts written from the order, the tracking and your help centre. You approve before anything sends.
Growth and upWhat a standalone helpdesk can't do from where it sits.
A helpdesk on its own only knows the conversation. Here every ticket sits on the same record as the orders, the projects and the client account.
AI answers from your own help centre
The chat assistant answers in your brand's voice from your published articles, with links to the ones it used, and from your product catalogue with product cards. It draws on the same credit pool as the rest of your AI, with no fee per resolved conversation.
Messenger and Instagram in the queue
Direct messages and comments from Facebook and Instagram arrive as tickets beside email and website chat.
A ticket becomes project work
A bug report or change request turns into a card on the delivery board in one click, linked back to the ticket and the client.
Routed to whoever looks after them
Tickets from a client go straight to their account handler, and the client can raise and follow tickets from the same portal as their projects and invoices.
Help centres for each audience
Public, client-only or internal, each on your own domain, mounted on your site or shared by a private link, in your own brand.
Articles that stay current
Review dates tracked per article, "was this helpful" on every page, and matching articles suggested beside the support form before anyone writes in.
A callback in seconds
When someone submits a form, your own line rings and they're connected the moment someone answers, with consent and daily limits built in.
When support knows, everyone knows.
A ticket isn't a dead end in another tool. Marketing holds the review request until it's solved, sales sees it on the renewal, and a bug becomes a card on the delivery board.
Which plan unlocks what.
Service is in every plan. Your customers, and everyone reading your help centre, never need a seat.
Core
£29 per Builder · £4 per Member a month
- One inbox for email and live chat
- A searchable help centre
- Macros and assignment rules
- Customer history beside every ticket
Growth
Most teams£69 per Builder · £6 per Member a month
- Everything in Core, plus
- Custom fields and access profiles
- SLAs and breach alerts
- AI answers from your help centre, with handover
- Playbooks that run across every team
- Dashboards that refresh themselves
Scale
Yearly£119 per Builder · £9 per Member a month
- Everything in Growth, plus
- Single sign-on and an audit log
- A sandbox to try changes
- A named manager and same-day fixes
- Multiple brands and legal entities
A five-agent support team on Growth. Five agents answer in Landing every day as Builders. Ten colleagues pick up escalations and see dashboards as Members.
Builders work in Landing every day. Members approve, pick up tasks and see dashboards. Customers and help centre readers are free. AI replies draw on a shared credit pool. Prices ex VAT.
Work out your priceBuilt for the questions IT, finance and your clients will ask.
A portal your clients trust, permissions your team can live with, and a record of who did what. The controls a bigger company checks before it signs.
A client portal in your brand
Clients see their projects, invoices, tickets and deliverables under your logo and colours, and everything public runs on your own domains.
Access profiles
Named permission sets for your team, your clients and your partners. A person can hold several, and every screen and every query respects them, so pay, margin and client data stay with the people allowed to see them.
Sign-in you can enforce
Two-factor by authenticator app, SMS or email, with recovery codes and a company-wide switch that requires it of everyone. Single sign-on on Scale.
Audit trails that stand up
Every signature carries the signer, the time, the IP address and a fingerprint of what was signed. Till sales sit in a chained log that shows any edit. Access changes and sign-in events are logged, with a full audit log on Scale.
Several brands, one account
Each brand keeps its own logo, voice, domains, emails, pages and chat assistant. Separate legal entities on Scale.
AI agents under your permissions
Claude and other assistants connect with "Sign in with Landing" and can only do what that person could do themselves. Read-only unless you say otherwise.
API, webhooks and exports
A documented public API for leads, bookings, chat, subscribers, tracking and embeds. Signed webhooks in, HTTP calls out from any playbook, and CSV and PDF exports from the screens that hold your data.
UK GDPR in practice
Consent kept word for word, one-click unsubscribe, a company-wide suppression list, retention rules on uploads, and a published list of sub-processors. Built in the UK by a UK company.
More on how we look after your data in Security, and who we work with in Sub-processors.
Questions support teams ask.
Anything else, ask us on the demo. We'll have your price worked out before you hang up.
Do customers need an account?
No. Customers write in by email or chat, and read the help centre, without a login. They're guests, and guests are free.
Can you move our Zendesk or Gorgias history?
Yes. History imported, macros rebuilt and the team trained, against success criteria agreed up front. Billing starts when we prove it's ready. How switching works.
Can the help centre run on our own domain?
Yes. Publish it on your domain, keep some articles internal, and link it from the chat widget so customers find answers before they ask.
Do AI replies send on their own?
Not unless you say so. Suggested replies are drafts; someone on the team approves them. AI use comes from the shared credit pool your Builders bring.
See your inbox with the context in it.
Thirty minutes on the helpdesk you use today and the tabs your team opens to answer a ticket, with your price worked out before you hang up.