- If the client base is strongly averse to automated callers
- Industry and community sentiment indicate that some clients will avoid providers that use automated receptionists; practices with such clientele should consider alternatives.
- If triage must be handled exclusively by humans
- Practices treating emergency or urgent triage as human-only may find limited value in automated triage; the product may still be useful for after-hours FAQs if configured conservatively.
- If procurement requires public security documentation
- Scritch does not publicly document SOC 2, ISO, data residency, or detailed security controls in accessible pages; organizations requiring these artifacts during initial procurement may prefer vendors with published trust centers.
- If the primary need is texting, reminders, and reviews rather than phone intake
- Platforms focused on digital client engagement (e.g., PetDesk, Weave) may better address texting and reminder workloads.
- If transparent self-serve pricing is required
- Scritch uses a demo/quote-based approach; buyers seeking predictable list pricing may find it harder to compare without engaging sales.
- Public roadmap and visibility
- No detailed public roadmap was found in accessible official sources.
- Key items to validate during a pilot
- PIMS integration specifics
- Which PIMS products are supported and whether integrations are native or workarounds
- Read/write permissions, auditability, and error-recovery behavior
- Emergency handling
- Decision logic for urgency and safe-failure behavior (for example, when transfer fails or the office is closed)
- Data retention and legal/compliance posture
- Retention periods for call recordings and transcripts and subprocessors used for telephony, transcription, and LLM services
- Caller ID and client matching accuracy
- Risk of misidentification with shared or changed phone numbers