Ringer Consumer Tasks

Scripts

Compose the task + strict schema (pure, offline, never dials):

node scripts/build-task.mjs \
  --playbook negotiate-bill \
  --values '{"company":"Xfinity","currentAmount":"95","goal":"lower","leverage":"AT&T Fiber offers $55/mo for the same speed; 4-year customer","walkAway":"yes","approvalMode":"ask"}' \
  --caller "Alex Rivera" --callback "+14155550100" > plan.json

For Quote Shootout, add --batch on a batchable playbook to get a per-business recipient_result_schema plus an aggregate call-level result_schema (cheapest business, potential savings):

node scripts/build-task.mjs --playbook get-quote \
  --values '{"service":"front brake pads + rotors, 2018 Honda Civic; out-the-door price","timeframe":"this week"}' \
  --batch > plan.json

For a non-English call, add --language (e.g. --language Spanish) so the task instructs the agent to run the whole conversation in that language, and pass the matching CALL-E --region/--locale to place-call.mjs (e.g. --region MX --locale es-MX). CALL-E supports English plus Hindi, Arabic, Vietnamese, German, Japanese, French, Spanish, and Portuguese in their respective regions.

Preview, then place (dry-run by default; --execute places the real call):

# 1) Dry run — prints the plan with masked numbers, places NO call:
node scripts/place-call.mjs --body plan.json --to-phone +14155550123

# 2) After consent — place it and wait for the structured result:
CALLE_API_KEY=calle_live_… \
node scripts/place-call.mjs --body plan.json --to-phone +14155550123 --execute --poll

# Quote Shootout: repeat --to-phone per business (batch is auto-detected):
CALLE_API_KEY=calle_live_… node scripts/place-call.mjs --body plan.json \
  --to-phone +14155550123 --to-phone +14155550188 --to-phone +14155550190 --execute --poll

Alternative placement: for a quick goal-only call without a custom schema, the CALL-E CLI works too — calle call start --to-phone +14155550123 --goal "<task>" then calle call status --run-id <run_id>. Use place-call.mjs (the API path) whenever you want the strict structured result this skill's schemas define.

Provider Boundary

This skill prepares and optionally executes CALL-E create-call requests of this shape (one call task; one or more recipients for batch):

{
  "task": "Composed from the playbook + user fields…",
  "recipients": [{ "phones": ["+14155550123"], "region": "US", "locale": "en-US" }],
  "result_schema": { "type": "object", "additionalProperties": false, "required": ["outcome"], "properties": { "…": {} } },
  "recipient_result_schema": { "…": "present only in batch / Quote Shootout" }
}

Result schemas are strict: CALL-E rejects any property not declared in properties before returning structured_result, so the output is always exactly the contract above.

Decision Authority (human-in-the-loop)

The negotiate-bill and cancel-subscription tasks encode who may say yes:

• Ask me (default): the agent may negotiate and capture the exact best offer but must not commit — it tells the rep the user will confirm shortly.
• Autonomous under a limit (approvalMode: "auto", autoAcceptBelow: <n>): the agent may accept an offer at or below the stated monthly amount.

Never place an autonomous-commit call without the user explicitly choosing it and setting the limit.

Safety Rules

Read references/safety.md for the full contract. Always:

• Treat a phone call as a real-world side effect; require explicit user intent.
• Require caller-provided E.164 numbers and region; never guess or repair them.
• Every generated task opens with a fixed AI disclosure (build-task.mjs states the agent must disclose it is an AI assistant at the start); do not remove or weaken it.
• Dry-run first; place a real call only after the user consents to that exact plan.
• Never invent account numbers, PINs, card numbers, or personal details; if asked for something not provided, the agent says it does not have it on hand.
• Do not make a binding commitment unless the user granted decision authority.
• Mask phone numbers in summaries; do not expose API keys or full numbers. The key is sent only to CALL-E's official host: place-call.mjs allowlists CALLE_BASE_URL (official *.heycall-e.com or localhost) and refuses to send the bearer token to any other origin.
• A live create carries a content-bound Idempotency-Key (a hash of the recipients + task + schema), so a lost response + rerun of --execute dedups instead of placing a second call.
• Do not claim a call happened or a result was achieved unless CALL-E returned it.
• Do not give medical, legal, financial, or emergency advice on the call.

References

• references/playbooks.md: every playbook's fields, option values, and result schema.
• references/safety.md: consent, PII, decision-authority, and phone-number rules.
• references/examples.md: worked end-to-end examples (compose → dry-run → execute) with sample structured results.