TC AI SUPPORT / KNOW WHEN TO ESCALATE
Fast answers when they are safe. Human ownership when they are not.
DaLong explains products, SiteGuard scope and findings, pre-sale choices, order progress and delivery state—then creates a human support path for sensitive, ambiguous or high-risk work.
Truth boundary: the robot cannot run a real SiteGuard scan, repair a site, approve a provider, move money or mark an order paid. Without the required backend contract it says what is missing and routes the next safe action.
SIX SUPPORT JOBS
The robot is useful because its authority is explicit.
Page explanation
Explains what each core product does, who it is for and where the buyer should go next.
Pre-sale guidance
Routes a buyer to SiteOS, SiteGuard, Payment, API Gateway, AI Support, GEO or the full website-to-payment answer.
SiteGuard triage
Clarifies monitoring scope, explains supplied findings and routes urgent or sensitive risk to a human.
Order status
Uses an order reference to query authoritative status; a chat statement can never become payment evidence.
Delivery explanation
Explains report fields, remediation guidance and next steps without claiming that a repair has happened.
Human escalation
Creates a ticket path with question context, risk category, related order or report and an audit-ready handoff.
THE SITEGUARD SUPPORT LOOP
From finding to explanation to accountable remediation.
DaLong keeps routine questions fast, but it never takes authority away from the scan runtime, the Payment Hub or a human responsible for high-risk remediation.
ROBOT AUTHORITY MATRIX
What DaLong may say, and what only another system may prove.
DaLong may
- Explain public products, plans and contractual boundaries
- Ask clarifying questions and route a buyer
- Explain supplied SiteGuard findings and remediation guidance
- Query server-authoritative order and delivery status
- Escalate to a human support ticket
explain(product) → allowed route(pre_sale_question) → allowed explain(supplied_finding) → allowed query(server_order_state) → allowed create(human_ticket) → allowed run(real_scan) → denied claim(repair_complete) → denied confirm(payment) → denied approve(provider) → denied move_money → denied
SCOPE THE SUPPORT LAYER
Tell us what DaLong should know—and when a human must take over.
This creates a review reference only. It is not an order, invoice or payment.
SUPPORT FAQ
Helpful without overclaiming.
Can DaLong run or schedule SiteGuard?
Not without a configured SiteGuard backend contract. It can explain the product, collect scope and route the request.
Can it answer order questions?
It can route to and query server-authoritative status when the required order reference and backend contract exist. It cannot infer paid state from a message or screenshot.
Is pricing active for this support layer?
No fixed price is claimed. It remains scope-based and checkout fails closed until an approved server price is activated.
START WITH A REAL QUESTION
Let DaLong explain the path. Let a human own the risk.
Open the robot for an immediate explanation, or submit the scoped request above for a review reference.