Getting Started
DMEDesk is an AI voice receptionist purpose-built for DMEPOS suppliers. This guide covers everything from initial setup to going live with your first AI agent.
Prerequisites
- An active DMEDesk subscription
- A phone number to forward to DMEDesk (or we can provision one for you)
- Your business details: company name, hours of operation, locations
Onboarding Timeline
| Day | Step | Details |
|---|---|---|
| 1–2 | Discovery Call | We review your call volume, workflows, and business rules. You provide your intake forms and scripting preferences. |
| 2–3 | Agent Configuration | We build your custom AI agent — greeting, call flows, escalation rules, and operating hours. |
| 3–4 | Integration Setup | Connect DMEDesk to your existing tools — CRMs, calendars, notification channels, and any DMEPOS-specific workflows. |
| 4–5 | Testing & QA | Run test calls across all scenarios. Verify data flows, escalation paths, and recording quality. |
| 5–7 | Go Live | Forward your main line to DMEDesk. We monitor the first 48 hours and fine-tune based on real calls. |
Phone Number Setup
You have two options for connecting your phone line to DMEDesk:
- Call forwarding — Forward your existing business number to the DMEDesk number we assign. This is the fastest option and requires no changes to your current phone provider.
- Number porting — Transfer your existing number directly to DMEDesk's telephony infrastructure. This takes 5–10 business days depending on your carrier.
Call Handling
DMEDesk handles inbound and outbound calls with AI-powered conversation management built specifically for DMEPOS workflows.
Inbound Call Flow
- Ring & Greet — Caller dials your number. DMEDesk answers within 2 rings with a custom greeting that includes your business name and AI disclosure (required by law in several states).
- Intent Detection — The AI identifies the caller's purpose: new order, reorder, delivery status, insurance question, prescription follow-up, or general inquiry.
- Information Gathering — Based on the intent, the AI collects the required information: patient name, date of birth, insurance ID, referring physician, equipment type, etc.
- Data Logging — All collected information is logged in your connected systems in real time — no manual data entry required.
- Warm Transfer or Resolution — If the call requires human intervention, DMEDesk transfers the call to your staff with a live summary so they never start from scratch. Otherwise, the AI resolves the call directly.
Call Types
| Type | Description | AI Resolution Rate |
|---|---|---|
| New Patient Intake | Full intake: demographics, insurance, equipment needs, physician info | ~85% |
| Reorder / Resupply | Existing patient reordering supplies (CPAP, diabetic, ostomy, etc.) | ~95% |
| Delivery Status | Patient checking on equipment delivery or shipping timeline | ~90% |
| Insurance Questions | Coverage verification inquiries, copay questions | ~70% (complex cases escalate) |
| Prescription Follow-Up | Missing Rx, expired prescription, fax status | ~80% |
After-Hours Handling
DMEDesk operates 24/7. After-hours calls follow the same flow but with adjusted escalation rules — urgent calls can be routed to an on-call number, while non-urgent calls are logged and queued for next-business-day follow-up with the caller receiving a callback confirmation.
AI Configuration
Every DMEDesk agent is configured to match your specific business requirements. The AI uses objective-based prompting — not rigid scripts — so it can handle unexpected caller requests naturally while staying within your defined guardrails.
Configurable Parameters
- Greeting & AI Disclosure — Customize the opening message. AI disclosure is mandatory and included automatically.
- Business Hours — Set operating hours per location. DMEDesk adjusts its behavior and escalation rules accordingly.
- Escalation Rules — Define when and how calls transfer to live staff: by topic, by caller frustration level, by specific keyword triggers, or by request.
- Required Fields — Specify which data points the AI must collect before ending a call (e.g., always get DOB + insurance ID for new patients).
- Equipment Catalog — Upload your HCPCS-coded product catalog so the AI can accurately discuss equipment, identify reorder needs, and capture correct item details.
- Location Routing — For multi-location operations, route calls to the appropriate staff or branch based on caller area code, ZIP, or stated location.
Voice & Personality
DMEDesk agents use natural-sounding AI voices. You can select from multiple voice options and adjust the conversational tone to match your brand — professional, warm, clinical, or casual. The AI adapts its language complexity based on caller cues.
Integrations
DMEDesk connects to 250+ tools through native integrations and API/webhook connectivity. Data flows are encrypted end-to-end, and any protected health information (PHI) is routed through HIPAA-compliant pipelines only.
How Integrations Work
When a call is completed, DMEDesk can automatically:
- Log the intake record in your connected systems
- Create a calendar event for follow-up
- Send a Slack or email notification to your team
- Update your CRM with the caller's information
- Trigger a follow-up workflow (e.g., send a confirmation SMS to the patient)
Supported Integration Categories
| Category | Examples |
|---|---|
| CRM & Sales | HubSpot, Salesforce, GoHighLevel, Pipedrive |
| Calendar & Scheduling | Google Calendar, Cal.com, Calendly |
| Communication | Slack, Microsoft Teams, Gmail, Twilio SMS |
| Automation | Webhooks, REST API, Zapier, Make |
| Forms & Data | Google Sheets, Airtable, Typeform |
Custom API / Webhook
For workflows not covered by native integrations, DMEDesk supports custom webhooks and REST API endpoints. You can push call data to any system that accepts HTTP requests. Full API documentation is provided upon onboarding.
Outbound Campaigns
DMEDesk isn't just for inbound calls. You can configure outbound call campaigns to automate patient follow-ups, prescription reminders, delivery confirmations, and reorder outreach.
Campaign Types
- Prescription Follow-Up — AI calls prescribers' offices to check on fax status, missing documents, or prior authorization updates.
- Patient Notification — Inform patients about delivery schedules, order confirmations, or required actions (e.g., "Your CPAP mask is eligible for resupply").
- Missing Documentation — Follow up with patients or facilities to collect missing paperwork (CMN, AOB, insurance cards).
- Reorder Outreach — Proactively contact patients approaching resupply windows for recurring equipment.
Campaign Configuration
Each campaign is configured with a contact list (uploaded via spreadsheet or connected CRM), a call script objective, operating hours, retry logic, and outcome tracking. Calls are placed in compliance with TCPA requirements — all contacts must have prior express consent, and opt-out is honored immediately.
Call Outcomes
Every outbound call logs a structured outcome: answered (with detailed notes), voicemail left, no answer, busy, or wrong number. Outcomes are written back to your connected spreadsheet or CRM automatically.
Compliance & HIPAA
DMEDesk is built with healthcare compliance at its core. Every feature is designed to meet or exceed HIPAA, TCPA, and CMS regulatory requirements for DMEPOS suppliers.
HIPAA
- Business Associate Agreement (BAA) executed with every client before go-live
- All call recordings, transcripts, and patient data encrypted at rest and in transit (AES-256 / TLS 1.3)
- PHI routed exclusively through HIPAA-compliant data pipelines — never through general-purpose automation tools
- Role-based access control: your team only sees what they need to see
- Automatic audit logging for all data access and modifications
TCPA / FCC
- AI voice = "artificial voice" under TCPA. DMEDesk includes mandatory AI disclosure on every call opener.
- Prior express consent required for all outbound calls. Consent records are tracked per contact.
- One-press opt-out honored immediately on both inbound and outbound calls.
- Consent revocation rules compliant with the April 2025 FCC update.
CMS Requirements
- DMEDesk provides an interactive phone presence — not an answering machine — as required by CMS for DMEPOS suppliers.
- Calls are answered live (by AI or transferred to staff), never sent to voicemail during operating hours.
- All interactions are documented and audit-ready.
State-Level AI Disclosure
Several states now require explicit AI disclosure during phone calls. DMEDesk's AI agent automatically identifies itself as an AI assistant at the beginning of every call, satisfying requirements in states like Texas (SB 140) and others with similar laws.
Analytics & Reporting
The DMEDesk dashboard provides real-time and historical visibility into your call operations.
Dashboard Metrics
- Total calls handled (inbound + outbound)
- AI resolution rate vs. escalation rate
- Average call duration
- Call volume by hour, day, and week
- Top call intents (intake, reorder, delivery status, etc.)
- Missed call rate and after-hours volume
Call Recordings & Transcripts
Every call is recorded and transcribed. Recordings are accessible from the dashboard with full text search across transcripts. All recordings are encrypted and retained per your configured retention policy (default: 90 days, configurable up to 7 years for compliance).
Exports
Export call logs, analytics summaries, and transcript data as CSV or PDF for compliance audits, internal reporting, or insurance documentation.
Troubleshooting
Calls not being answered
Check that call forwarding is active on your phone provider. Verify the forwarding number matches the DMEDesk number assigned during onboarding. If using number porting, confirm the port has completed with your carrier.
AI not collecting required information
Review your agent configuration under "Required Fields." Ensure the fields are marked as mandatory and that the AI prompt includes instructions to collect them. Contact support if the issue persists after configuration changes.
Data not syncing to connected tools
Check the integration status in your DMEDesk dashboard under Settings → Integrations. Look for error indicators or failed sync attempts. Common causes: expired API tokens, changed webhook URLs, or rate limiting from the destination service.
Poor call quality or latency
Call quality depends on the caller's phone connection, not DMEDesk's infrastructure. If you receive reports of choppy audio, check if the issue is consistent across all calls or isolated to specific callers. For SIP-based connections, verify your network supports the required bandwidth and ports.
Need help?
Glossary
| Term | Definition |
|---|---|
| AOB | Assignment of Benefits — patient authorization allowing the supplier to bill insurance directly |
| BAA | Business Associate Agreement — HIPAA-required contract between covered entities and their service providers |
| CMN | Certificate of Medical Necessity — physician-signed form required for certain DME items |
| CPAP | Continuous Positive Airway Pressure — a common DME product for sleep apnea treatment |
| DMEPOS | Durable Medical Equipment, Prosthetics, Orthotics, and Supplies |
| HCPCS | Healthcare Common Procedure Coding System — codes used to identify DME products for account |
| LCD | Local Coverage Determination — Medicare contractor-level coverage policy |
| NCD | National Coverage Determination — CMS-level coverage policy |
| NPI | National Provider Identifier — 10-digit number identifying healthcare providers |
| PECOS | Provider Enrollment, Chain, and Ownership System — Medicare enrollment database |
| PHI | Protected Health Information — any health data tied to an identifiable individual |
| Prior Auth | Prior Authorization — insurer approval required before coverage of certain equipment |
| TCPA | Telephone Consumer Protection Act — federal law regulating automated calls and texts |