Internal Staff Guide
This guide is for Dynaris internal staff supporting customers, troubleshooting, and managing launches. Dynaris exists so customers never miss an inquiry, never drop a follow-up, and never lose a lead. When something breaks, that promise is at risk. Prioritize accordingly.
Roles and Responsibilities
| Role | Focus |
|---|---|
| Support | Customer questions, troubleshooting, connector issues |
| Onboarding | New customer setup, channel configuration, launch verification |
| Engineering | Backend, integrations, Composio, gateway |
Key Systems and URLs
| System | URL | Purpose |
|---|---|---|
| App | app.dynaris.ai | Main application |
| Docs | docs.dynaris.ai | Documentation (this site) |
| Auth | auth.dynaris.ai | OAuth, Composio connection links |
| Gateway | AI_BACKEND_URL | Integrations, toolkits, process-events |
Integration Architecture (Reference)
- Composio -- OAuth and API connections for Gmail, Slack, HubSpot, Google Calendar, WhatsApp, and 200+ tools
- Twilio -- Dedicated Dynaris API routes for voice (account, connect, disconnect, assign/unassign)
- WhatsApp -- Meta Business API via Composio;
composio.whatsapp_connectionstable - Gateway --
/api/integrations/toolkits,/api/process-events, etc.
Onboarding Checklist (Staff)
When onboarding a new customer:
-
Account
- Confirm sign-up and email verification
- Note plan/credits
-
Channels
- Gmail / Outlook: OAuth via Composio
- Slack: OAuth via Composio
- Twilio: Connect via Dynaris Voice page; assign number
- WhatsApp: Meta Business API; templates must be approved first
-
Knowledge Base
- Ensure at least one document or FAQ is uploaded
- Verify content matches their use case (sales, support, etc.)
-
Calendar
- Google Calendar or Outlook calendar connected
- Test availability lookup
-
CRM (if applicable)
- HubSpot or Salesforce connected
- Verify contact sync
-
Launch verification
- Run through Launch Guide Post-Launch Verification
- Document any custom config
Troubleshooting Reference
Critical: Inquiries Not Being Responded To
When a customer reports that leads are not getting replies, follow-ups are not sending, or calls are not being answered, treat this as high priority. The core value proposition is continuous response.
- Email not replying: Check Gmail/Outlook connection; verify triggers; confirm Auto Mode is on if they expect automatic replies
- Follow-ups not sending: Check workflow/schedule; verify contact has correct status; confirm sequence is active
- Calls not answered: Twilio webhook, number assignment, voice agent config
- Chat/WhatsApp not engaging: WhatsApp connection; template approval; 24-hour window status
OAuth / Connectors
- Connection fails: Check auth.dynaris.ai logs; verify redirect URIs
- Token expired: Customer must reconnect via Connectors (Reconnect)
- Missing permissions: Some apps require additional OAuth scopes; check Composio config
Twilio / Voice
- No answer: Verify webhook URL in Twilio points to Dynaris; check number assignment
- Wrong agent: Confirm Voice Agent is assigned to the number in Dynaris
- Audio issues: Check Twilio region, codec; review voice agent prompt for clarity
- Template required: First message to a user must use approved template
- 24-hour window: Free-form messages only within 24 hours of user reply
- Meta rejection: Template may violate policy; refer to Meta guidelines
Events Not Processing
- Auto Mode off: Events queue until manually processed
- Integration disconnected: Check Connectors status
- Trigger not configured: Some events require explicit trigger setup
- Gateway/process-events: Check backend logs for failed event processing
CRM Sync
- Contact not syncing: Verify CRM connection; check contact matching (email/phone)
- Duplicate contacts: Review merge rules; ensure consistent identifiers
Escalation Paths
| Issue Type | Escalate To |
|---|---|
| OAuth / Composio | Engineering |
| Twilio / Voice | Engineering (webhook, config) |
| WhatsApp / Meta | Engineering (API, templates) |
| Billing / Credits | Billing team |
| Feature request | Product |
Documentation Updates
When adding or changing integrations:
- Update the relevant integration page (e.g.,
/docs/integrations/whatsapp) - Update Integrations Overview if adding a new integration
- Update System Architecture if flow changes
- Update Launch Guide if launch steps change
Customer-Facing vs Internal
| Document | Audience |
|---|---|
| Introduction, Getting Started, Features, Guides | Customers |
| Integrations (Gmail, Slack, Twilio, WhatsApp, etc.) | Customers |
| Launch Guide | Customers + Staff |
| Why Dynaris, System Architecture | Customers + Staff |
| Internal Staff Guide | Staff only (linked from Launch Guide) |