there24
Always-on product support

Stop hiring an L1 to mute Slack.Hire twelve instead.

L1 triage on lean routes. L2 investigation that opens PRs. L3 architecture for refactors. Voice for the phone. Each tier picks its own route and deploys exactly where it earns its place. The review gate is locked on every plan.

See the mechanism →
ChatScreenshareVoicePull requestReview gate
L1·L2·L3Tiered triage to architecture
Always-onChat → live → engineering
ReviewedIndependent gate every plan
Get started · 01

A support journey, not a setup form.

01

Chat starts the case

A calm support surface opens inside the customer's product or portal.

02

Context is collected

The agent asks only for the missing details and keeps every answer attached to the case.

03

Live help begins

Screenshare, voice, or video call can start from the same conversation.

04

Engineering gets evidence

Repos, logs, screenshots, and transcript are organized into a handoff your team can trust.

The mechanism · how a run actually works · 02

Investigate. Fix. Verify. Ship.All inside the time it takes you to read this sentence.

there24 · run orch-2k9f7cost $0.00Investigating
Run trace inbound
»Investigate
→POST /v1/embed · origin allow-listed
→CORS locked · no key in the browser
→agent_token resolves to Bolt · L1 triage
→intent · "checkout stuck after payment"
→transcript + browser details attached
»Fix
→sandbox spun up · overlay clone of repo
→orchestrator orch-2k9f7 online
→indexing code graph · 1247 nodes / 4892 edges
→preamble assembled from 3 similar resolutions
→dispatch sub-agents · Atlas · Trace
→hypothesis · confirmation poll never resolves
→patch drafted · checkout/confirm.ts
»Verify
→review pass on a fresh session
→separate instructions · gate locked
!1 blocking comment · null-guard missing
→fixer re-runs · attempt 2 · we never give up first
✓review · no blocking comments · green
»Ship
→branch run/2k9f7 · tests green
✓PR #4812 opened · no auto-merge
→customer notified · fix delivered as a tick-list
→run classified into your learnings pool
Artifacts
01Embed · inboundagent_token → Bolt
The card charge succeeds, but the confirmation page keeps spinning.
agent_token→ resolves to Bolt · L1
02Sandbox · orchestratororch-2k9f7
1247nodes
4892edges
AtlasTrace
checkout/confirm.ts
-poll(() => status === 'paid')
+poll(() => status === 'paid', { onTimeout })
+if (!order) return redirectToReceipt()
03Review gatefresh session · locked
🔒Independent pass · separate instructions · no shared context with the fixer
!attempt 1 · null-guard missing
✓attempt 2 · null-guard added
No blocking commentsgreen
04Pull requestawaiting merge
⑃
PR #4812 · fix checkout confirmation poll
run/2k9f7 → main · awaiting operator merge
Confirmation resolves on paid status
Fallback redirect to receipt
No auto-merge · in your operator queue · cost $0.31
01Investigate
02Fix
03Verify
04Ship
One run, the right altitude · 03

Every tier picks its own route.

L1 triage on lean routes. L2 investigation that opens PRs. L3 architecture for refactors. Voice for the phone. The orchestrator deploys each exactly where it earns its place, and the review gate stays locked on all of them.

L1Bolt
Triage
→ lean route · FAQ + simple fixes

Answers the known questions and clears the easy tickets before they ever reach a human.

Deploys on lean routes
L2Ember
Investigation
→ root-cause · opens PRs

Reproduces the bug, reads the repo, drafts a patch, and opens a pull request your operator merges.

Deploys where root-cause lives
L3Atlas
Architecture
→ deep tech · refactors + debugging

Takes the hard, cross-cutting problems: the refactors and systemic debugging that need real depth.

Deploys deep in the codebase
VoiceLive
The phone
→ human escalation · spoken

Picks up the call when a customer would rather talk, and keeps the same case, context, and evidence.

Deploys when it counts
One thread, every channel · 04

Escalate without losing the thread.

A case can start in chat and move to screenshare, voice, or video, the same conversation, the same evidence, the same case. Live help begins from inside the support surface, never a cold restart.

01
Chat
the entry point

A calm support surface opens inside the customer's product or portal.

02
Screenshare
see it live

See exactly what the customer sees, in real time, from the same conversation.

03
Voice
for the phone

Pick up the call when talking is faster than typing, same case, same context.

04
Video
face to face

Jump to a video call for the hard escalations, with the transcript carried along.

one caseSame case · transcript · evidence, carried across every channel.
Six personas, one orchestrator · 05

Pick the role. We run the workflow.

Every persona is a support policy, not a prompt. Bolt handles intake; Atlas handles deep architecture. Independent review stays on every plan before anything ships.

BoltL1 triage · FAQ · simple fixes
EmberL2 root-cause · opens PRs
AtlasDeep tech · refactors · debugging
VegaFrontend · visual + interaction bugs
TraceTests · writes · runs · maintains
CompassResearch · planner · feature spec
Independent before ship
The review promise · 06

Every run is reviewed. We pay for it. You ship the PR.

01

Independent review checks every diff before it leaves the sandbox. Fresh session. Separate instructions. Locked gate.

checked before it leaves
02

Free tier included. Not a feature flag. Not a paid add-on. We don't ship regressions to your customers to save a few cents a run.

included on every plan
Review stays independentGate locked · no auto-merge
Deploy anywhere · 07

One script tag, or its own front door.

Drop it into the corner of your product, or stand up a full there24 support portal with its own URL, no build required. Same agents, same review gate, wherever your customers arrive. No key in the browser, ever.

EmbeddedIn-product widget

One script tag in the corner of your product or app.

HostedIts own front door

A there24 support portal at your own URL, no build required.

ScopedCustomer portals

A dedicated portal per customer, account, or workspace.

VoiceA phone line

A number that reaches the same agents and the same case.

index.html · the fastest path
<!-- there24 · embedded support --><script src="https://cdn.there24.app/embed.js" data-agent="agent_token" defer></script>
CORS locked to your originsScoped endpointNo extra customer setupNo auto-merge ever
Engineering receivesevidence intact
  • ✓Repo + branchrun/2k9f7 · overlay clonegit
  • ✓Logs + console tracescoped to the runtrace
  • ✓Screenshots + recordingcaptured in the sessionmedia
  • ✓Full handoff transcriptchat → live → engineeringthread
  • ✓Steps to reproduceorganized, not rawrepro

Talk to there24 Specialist

From chat to a reviewed pull request.

A product support specialist who can explain L1 to L3 triage, the review gate, and how fixes ship.

there24Concierge

A product support specialist who can explain L1 to L3 triage, the review gate, and how fixes ship.

Start a conversation

Support questions

there24, answered.

What is there24?

there24 is autonomous product support that goes from chat to live debugging to a reviewed pull request. It is repo-aware, triages across L1 to L3, brings in voice when it counts, and keeps an independent review gate on every plan.

Can AI support actually fix bugs?

Yes. there24 does not just answer questions. L2 investigation opens pull requests and L3 architecture handles refactors. An independent review gate checks every plan before anything ships, so fixes reach engineering with the evidence to act.

How does there24 escalate without losing context?

A case can start in chat and move to screenshare, voice, or video as the same conversation, the same evidence, the same case. Live help begins from inside the support surface, never a cold restart.

How do the support tiers work?

Every tier picks its own route. L1 handles triage on lean routes, L2 runs investigation that opens PRs, L3 covers architecture for refactors, and voice covers the phone. The orchestrator deploys each one exactly where it earns its place.

What is the review gate in there24?

Every run is reviewed before it ships, and OneOrigin pays for that review. The gate stays locked on every plan, because there24 does not ship regressions to your customers to save a few cents a run. You ship the PR.

How is there24 deployed and is it secure?

You drop in one script tag, or stand up a full there24 support portal with its own URL, no build required. The same agents and the same review gate work wherever your customers arrive, and no key is ever in the browser.

Always on · chat first · live when it counts

Support that moves from chat to live debugging, without losing the thread.

Give every customer a polished entry point, escalate hard issues into screenshare or video, and hand engineering the evidence to act. Independent review on every plan.

See the mechanism →

Free for 3 issues / month · L1 support · watermarked. Independent review is included on every plan.