21/Pj·Projects·Work & people
The work you plan.
The work that arrives.
Issues, sprints, gantt roadmaps, SLAs. Product work, internal projects, and the tickets your customers send you — handled by the same queues, the same boards, and the same database as the rest of your business.
Included in Pro and above·No credit card
31 of 42 pts
day 8 of 10
Mobile checkout flow
Speed up product page
Pickup window picker
New email template
POS receipt logo
01/One engine
Customer support, internal projects, platform requests. One engine.
A queue is three decisions, and then it runs: the same lifecycle engine, the same boards, whether the work came from a customer, a colleague, or another system.
- 01
An audience
Customer, internal, or platform. Switch audiences and the chrome changes; the engine underneath does not.
- 02
A default issue kind and a reference prefix
WEB-098, OPS-042: every issue carries a name people can say out loud.
- 03
The channels you accept on
Email, web form, DM, API. Cross-queue dashboards roll up health and SLA at a glance.
02/Issues
Every issue knows about the rest of your business.
An issue tracker on its own island has to be told everything. This one reads the customer, the order, the product, and the booking straight off the rows they already live in — so the bug knows who reported it before anyone types a word.
- Linked customers, orders, products, and calendar bookings
- Custom fields, statuses, and lifecycles per queue
- Threaded comments, attachments, watchers
- An activity feed that shows who did what — with Sebastien's suggestions inline
Speed up product page LCP under 1.8s
- Assignee
- Marcus L.
- Priority
- High
- Points
- 3
- Sprint
- 12 · Web
- Due
- Fri May 30
- Customer impact
- all visitors
- ├Marcus moved this to In progress · 2h ago
- ├Sebastien identified 3 candidate slow queries · view
- └Sarah linked support ticket #4029 — same root cause
03/Sprints
Plan, commit, run, retro — without a separate tool.
The sprint is the unit of a team's week. It lives here, beside the customers and the orders the work is for, not in a tab you export from.
- 01
Plan
Drag from the backlog into the next sprint. Capacity-aware, by team and by individual.
- 02
Run
Burn-up, burn-down, and velocity over time. Carryover rules decide what rolls forward.
- 03
Retro
A built-in retro template tied to the sprint it reviews — the retro knows what shipped.
04/Roadmap
Quarter-level planning that stays connected to the day's work.
Lay initiatives out on a timeline. Drag a bar to re-plan and the sprints and issues linked underneath move with it. Hand stakeholders a read-only view — no slide, no export, no version of the roadmap that was true last Tuesday.
05/Support
Tickets where they belong: beside the customer's order and history.
Email, web form, in-app messages — all land in the same queue, on the same board, as the rest of the team's work. SLA timers stay visible; escalation rules are built in. Reply inline, link the order, attach the receipt, close the loop. The customer never sees the seam.
SdSupport deskQueues, boards, SLAs, CSAT, automations — support on the same customer record.- open
Order #1042 — never arrived
Maria Lopez · Email · 12m ago
SLA23m left - open
Question about subscription pause
Eva Stein · DM · 1h ago
SLA47m left - in progress
Kitchen display offline
Reese Cole · Web form · 4h ago
06/Sebastien
Drafts the reply before you open the ticket.
Sebastien has the same tools you do. It pulls the order, the tracking, the policy, and the past conversation, and proposes a reply for your approval. Send as-is, edit, or pivot. It will also triage, link related work, summarize a thread, or propose due dates — you stay in charge; it removes the toil.
- “triage what came in overnight”
- “link the tickets with the same root cause”
- “summarize this thread”
- “propose due dates for the backlog”
›My order #1042 hasn't shipped. Where is it?
- ├order #1042 · Maria Lopez · paid 3 days ago · UPS · shipped yesterday 06:02
- ├tracking: out for delivery · expected today by 3:30pm
- ├policy and the last conversation read
- └draft ready · nothing sent yet
Hi Maria — your order shipped yesterday and UPS shows it out for delivery today by 3:30pm. Tracking: 1Z999AA10123456784. Reply here if it doesn't arrive.
every reply logged with the tools Sebastien used
07/Connected
Project management that sees the whole business.
When projects, support, sprints, and customer history live in one place, you stop translating between tools. The bug ticket knows the customer who reported it. The roadmap knows what's in flight. The retro knows what shipped.
Instead of Jira + Linear + Zendesk + Intercom
- 01
One engine, three audiences
Internal projects, customer support, and platform requests — same lifecycle engine, same boards. Switch audiences; the chrome changes.
- 02
Sebastien does the boring parts
Triage, draft replies, link related work, summarize threads, propose due dates. You stay in charge; it removes the toil.
- 03
Connected to everything
Tickets see orders. Issues see the calendar. Sprints see HR. No exports, no syncs, no integration that breaks tomorrow morning.
Projects · included in Pro and above
Done.
Fourteen days free, no card. Your first board in three minutes — with the customers, orders, and calendar it will link to already there.