Staff Docs
Campaigns, Data Pool, Team Access, and Operations Control with button directions and screenshot slots.
The support docs are the people-friendly guide for the DWS tools. Use it to sooth your frustrations if you had it with us, find the solutions to your favorite problems and bugs, and find the right pages for everything...all without bothering your favorite business solutions tech support--Or, well, before you do, anyway.
Use the role-based pages when you want user docs and staff docs separated into the routes people actually move between.
Campaigns, Data Pool, Team Access, and Operations Control with button directions and screenshot slots.
Dashboard, Dialer Control, Billing Records, and Payment Portal directions with visual placeholders.
Known error patterns, recurring bugs, report templates, and escalation directions for staff and users.
Public status summary for page health, active problems, ETA language, and support email handoff.
Short answers to the questions people ask before they need a walkthrough.
Use Campaigns. The file input is labeled Import Leads CSV. Data Pool is the place to review and export those leads after the import.
Platform staff use Operations Control for broader platform tools and Team Access for org-level memberships.
Customers and users go to Billing Records. New charges and subscription actions go through the Payment Portal.
Check whether the operator shows READY first. Browser mode now requires Chrome on desktop with a wired headset, and phone operator mode now waits for the operator to call the Twilio number inbound before prospects can rotate.
The current workflow is campaign-based. Import into the campaign. Use Data Pool to inspect or export the lead records that exist in the system.
Internal workflows for owners, developers, ops, and support staff.
READY when the prospect was dialed.Start Call, called the displayed Twilio number from the registered phone, and waited for READY.Plain-language direction for org admins, agents, and customers.
Org admins typically handle team access for their own organization, review lead work, and direct agents to the right operational pages.
Agents mostly use Dialer Control and sometimes Data Pool if their page access allows it.
Customers use Billing Records, Invoices, Past Payments, and Payment Portal.
Check whether the account has page access, whether the correct organization is selected, and whether the user is on the right route for their role.
These pages are intentionally public so staff can paste links into chats, tickets, or handoff notes without creating another permission barrier.
Purpose, primary audience, and route references for the main pages.
Create campaigns, manage settings, assign teams, and import lead CSVs.
Browse leads, filter them, review outcomes, and export CSVs.
Run manual or auto dial sessions, manage calls, and watch live runtime notes.
Manage organization memberships, roles, and team login access.
Platform-level user tools, org controls, and page-access administration.
User-facing history page for invoices and payments already on file.
Handle charges, subscription status, and customer payment actions.
Public documentation for answering operational questions without requiring login.
Starter reference for the main buttons, links, and actions on the major pages. Audit the copy when the UI changes.
It covers the visible controls on the main routes. Row-level actions that only appear after data loads can vary by record, so treat this as the first-pass manual rather than the final source of truth.