Who answers my visitors when Codus is closed?
When your desktop is unavailable, Codus can answer visitors from the cloud using your published help pages, a current support brief and the conversation. Approved account information may also be available for a verified signed-in visitor. The cloud responder does not have your repository or local files.
Before you start
Your support instance must be bound to the correct project and have a fresh support brief and available cloud-answering budget. Publishing current answers and refreshing the brief are separate tasks; updating one does not automatically prove the other is current.
Prepare after-hours answers
- Open the project's chats tab and expand instances.
- Confirm the instance is bound to the intended product.
- Ask the project agent to review and publish the product's answer library. See maintaining support answers.
- On the instance card, choose generate brief or regenerate brief. Wait for the operation to finish and check the displayed age.
- Review the instance's cloud budget before testing coverage.
Generating a brief and answering in the cloud use AI services. Check the applicable usage and budget rather than assuming an unlimited free service.
What the cloud can and cannot do
Published answers provide detailed product guidance; the brief supplies broader context. Account-aware answers require a verified identity and a configured, approved data connection. A visitor typing an email address is not identity verification.
A bug or a question needing human judgement can be recorded for the team. That is not a promise of an immediate human response, a completed fix, an external GitHub issue or an email notification. The cloud must not invent pricing exceptions, refunds or actions it cannot perform.
If a conversation is waiting
A missing or stale brief, exhausted budget, unavailable data or a question outside the available knowledge can require the team. Check the conversation and instance status rather than repeatedly resending a test. A fresh brief does not replace missing help pages.
When a desktop becomes available again, its support work can resume. Do not equate reopening the app with proof that every waiting conversation has already been answered.
How do I know it worked?
With permission to send a test, check that the widget receives an appropriate answer and that the same reply appears in chats. Cloud replies are identified there. Verify delivery and content, not merely the existence of a new brief.