DeyoDeyo user guide
From first setup to daily support operations.
Follow the practical sequence for connecting knowledge, testing answers, publishing the widget, handling human conversations, and maintaining a workspace.
1. Start with a workspace
Deyo is a web customer messenger that answers from registered knowledge and keeps the same conversation when a teammate must take over.
- Create or choose a workspace.
- Add the latest customer-facing material before internal archives.
- Use Playground before exposing the widget to customers.
2. Add trustworthy knowledge
Use websites for maintained public documentation, files for stable reference material, and Q&A for answers whose wording and exceptions must be explicit.
- Supported files: PDF, Markdown, TXT, JSON, JSONL, and CSV.
- Remove obsolete or conflicting policies before import.
- Review processing state and retry failed imports instead of assuming they are ready.
3. Test answer quality
Test easy questions, paraphrases, and questions Deyo should not answer. Review the cited source and the resulting handoff state, not just the prose.
- Confirm prices, dates, and exceptions against the source.
- Mark incorrect AI answers for review.
- Add or revise Q&A when a critical answer needs stronger coverage.
4. Configure and publish the widget
Set the display copy and allowed domains, copy the workspace installation script, then validate it on the real production origin.
- Load the script once in the customer-facing application shell.
- Verify desktop, mobile, and keyboard behavior.
- Confirm that an unapproved origin cannot bootstrap the widget.
5. Operate human handoff
A handoff belongs in the same conversation. Slack and email are notification channels; teammates review context and reply from Deyo Inbox.
- Define business hours and the correct timezone.
- Send a test handoff to every configured recipient.
- Close the conversation or return it to AI only after the customer has a clear outcome.
6. Improve from real conversations
Review handoffs, negative feedback, and knowledge-gap signals regularly. A lower handoff rate is not automatically better if customers need account-specific help.
- Compare the answer with the current source.
- Separate missing knowledge from questions that require human authority.
- Retest representative questions after updating a source.
7. Manage plan, team, and data
Workspace roles, subscription state, usage, and deletion are operational controls. Verify the current plan before relying on a limit shown in a guide.
- Invite only people who need workspace access.
- Review AI conversation and knowledge usage before upgrading.
- Read the current Terms and Privacy Policy before deleting a workspace or account.