ReplyGuard

Check a draft against the conversation before you send it.

ReplyGuard compares a draft reply with the conversation it answers. It flags missed questions, accidental commitments, unsupported factual claims, ambiguous wording, repetition, and avoidable tone problems. A successful run returns structured findings plus a conservative corrected reply.

Why use it

• Add a pre-send quality gate to support, sales, or operations workflows.
• Catch promises and dates that the received thread does not support.
• Receive both JSON findings and copy-ready corrected text.
• Run one bounded analysis through the Apify API, schedules, webhooks, or MCP.

Input

Provide thread, proposed_reply, and an optional tone of preserve, warm, direct, or concise. Questions in the thread do not establish their proposed answers as facts.

Output

The default dataset contains one item with status, summary, findings, and corrected_reply. Evidence is constrained to exact fragments from the input. When a generated correction cannot be validated, ReplyGuard supplies a neutral holding reply instead of guessing.

Self-service run and recovery

No separate Dravara account, API key, integration, or support handoff is required. Complete the Actor input, start one run, and open its default dataset to read the result. ReplyGuard never sends the draft or updates another system.

If input validation fails, correct the named field and start a new run. If the analysis service is temporarily unavailable, wait a few minutes and start one new run; a failed run does not continue in the background. If a charge or dataset state ever looks unclear, do not loop automatic retries: inspect that run's Charges, default dataset, and Self-service failure details output first. The failure output is the sanitized key-value-store OUTPUT record with the stable error code, retry guidance, and next action.

Billing

Dravara's creator charge for a successful run is $0.20005: the $0.00005 apify-actor-start event plus $0.20 for reply-analysis-created. Apify separately passes its variable platform usage to the customer and determines the final displayed total; Dravara does not reduce its creator charge to absorb that usage. The result event is captured only after a result is available in the run dataset. Invalid inputs and provider failures skip the result charge, but the Actor-start charge and Apify platform usage can still apply. The synthetic sample input is billed like any other run.

Privacy and limits

Inputs are processed by Dravara, LLC's private service and the OpenAI API using store: false; applicable provider abuse-monitoring retention may still apply. Apify retains normal run input/output under the runner's plan and retention settings. Do not submit passwords, API keys, payment data, health data, or unrelated customer content.

Maximum input sizes are 20,000 characters for the thread and 10,000 for the draft. No message is sent on the user's behalf.

Optional defect contact: support@dravarahq.com. Send only the Apify run ID and safe error text, never the input. Support does not complete or deliver failed runs.