Tickets are queued and answered in a daily batch. Nothing is lost. The response window is the intended service level and is still being finalized — not yet a live commitment. The email inbox below is live and receives messages; a reply from it is not yet guaranteed.
where possible so the response is auditable and shareable with your team. The Onboarding guide and the Customer FAQ cover most setup and operating questions self-serve.
sets the next step clearly rather than over-explaining the timeline.
| Channel | When to use it |
|---|---|
| In-product chat (Crisp, embedded into the agency dashboard) | Primary channel during the beta cohort. Activated when the operator provisions the chat account. |
| Reach us at support@doptar.com — this inbox is live and receives messages sent to it. Use it as the fallback channel when in-product chat isn't provisioned. | |
| Loom demo | Static walkthrough covering install → authorize → dashboard → scan → findings → export → disconnect. |
External issue trackers, GitHub-style public issues, voice / phone hotline, and synchronous chat outside the in-product channel are out of scope for the alpha and beta cohorts.
Aggregate counts, severity distributions, and metadata-only audit findings tied to your install. We do not store message bodies, contact identifiers, or any client-account PII. Full list: Privacy §3.
No. The detectors read only direction enums (inbound / outbound) and timestamps. Message bodies, recordings, and transcripts are never read into application memory and never persisted. Full statement: Privacy §4 and Scope of Access §4.
No. Doptar is read-only for your CRM business data: there is no CRM-data write scope or write code path anywhere in the Service. (It requests two OAuth control-plane scopes — oauth.readonly to list your installed client accounts via GET /oauth/installedLocations, and oauth.write to mint per-location tokens via POST /oauth/locationToken; neither writes CRM data.) Full statement: Scope of Access §6.
No. Findings are diagnostic indicators only. The Service does not aggregate the opportunity monetary value field, does not produce financial impact estimates, and the AI summary is post-checked for revenue-extrapolation phrasing. Full statement: Scope of Access §7.
The AI summary is an agency-review draft, not a deliverable. It runs over metadata only, is pre-checked for PII patterns, has hard-coded system-prompt constraints, and is post-checked for forbidden phrasing. Edit the draft before sharing it. The rule-based findings underneath are the source of truth.
Yes, after your own review. The CSV export is the intended sharing artifact; the AI draft is intended as a starting point for your own client report.
Your session is cleared and the Service stops calling the platform on your behalf. Your agency record is retained as an audit log entry. Tokens stay encrypted at rest until the operator rotates the encryption key on your written request. Full detail: Privacy §9 and Onboarding §10.
You complete checkout on the payment provider's hosted page. Within 24 business hours a staff operator reconciles the checkout against your agency record and toggles your payment status to paid. We never hold card data. Full flow: Onboarding §9.
We describe our data-handling posture precisely rather than assert a certification we do not hold. The Service does not consume the data categories that trigger the core surface of the major messaging regulations (no message bodies, no contact PII, no recordings). Your own use of the platform and any actions you take on findings remain your responsibility. Full statement: Terms §12.
The alpha and early-beta cohorts are tuned for agencies managing 5–50 client accounts. If your install is significantly larger, contact support before running the first scan so we can confirm the scan duration and rate-limit posture for your tenant. A larger tier is planned.
A short summary of how support tickets move through the queue:
Onboarding guide or the Customer FAQ.
retry, no findings, false-positive concern, billing question) receive a templated reply within the 24-hour window.
access, or billing disputes are reviewed internally before a reply leaves. The response time stays within the intended window; the internal review adds depth, not delay.
There is no on-call rotation in the alpha and early-beta cohorts. After-hours messages are answered at the next business-day batch within the intended 24-hour window.