do-not-call
Skill0 starsChanged 2 months agoMITView on GitHub
Enforce Do Not Call on Talkif — add and remove numbers, bulk-import a suppression list, check numbers before building a campaign, wire an unsubscribe flow to the API, and understand where the check runs. Use for compliance code and for keeping Talkif in sync with your CRM's opt-outs.
In this repository22 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- api-conventionsSkill
- choose-models-and-voicesSkill
- create-campaignSkill
- create-flow-functionSkill
- create-flowSkill
- create-scheduleSkill
- handle-inbound-callsSkill
- make-callSkill
- manage-contactsSkill
- manage-phone-numbersSkill
- quickstartSkill
- read-billingSkill
- read-call-resultsSkill
- realtime-eventsSkill
- setup-api-keySkill
- test-a-flowSkill
- troubleshoot-callsSkill
- update-flowSkill
- verify-webhooksSkill
- web-callsSkill
- write-promptsSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 36
Registry refresh: Import your regulatory suppression list with POST /dnc/bulk (10,000 per request) on its cycle.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Do Not Call list
Concepts
The DNC list is a per-account list of phone numbers, checked before every outbound call — direct, campaign, schedule, API, Meta lead. On the list → the call is refused (contact_on_dnc_list) or, in a campaign, the contact is skipped with reason dnc_list. No per-call override. Inbound calls from a listed number are still answered. It is not a contact flag: deleting a contact doesn't block their number; this does.
Endpoints
| SDK | |
POST /dnc { phoneNumber, reason?, source? } | doNotCall.addDncEntry / do_not_call.add_dnc_entry |
POST /dnc/bulk { phoneNumbers[1..10000], reason?, source? } | bulkImportDnc |
POST /dnc/check { phoneNumbers[1..100] } → { results: { "+1…": true } } | checkDncStatus |
GET /dnc?search=&source=&limit=&offset= | listDncEntries |
DELETE /dnc/{phoneNumber} | removeDncEntry |
source records provenance: manual, api, call_opt_out (the person asked during a call), bulk_import. Use api from your own systems.
await client.doNotCall.addDncEntry({ phoneNumber: "+15551234567", reason: "Unsubscribed via email", source: "api" });
const { results } = await client.doNotCall.checkDncStatus({ phoneNumbers: numbers.slice(0, 100) });client.do_not_call.add_dnc_entry(phone_number="+15551234567", reason="Unsubscribed via email", source="api")Patterns
- Unsubscribe webhook →
POST /dnc. Talkif can't see a stop request that landed in your inbox or CRM; the moment your system records one, add the number. - Scrub before a campaign.
POST /dnc/checkin batches of 100, so your "contacts to call" count is right and skipped rows don't surprise anyone. - Registry refresh. Import your regulatory suppression list with
POST /dnc/bulk(10,000 per request) on its cycle;reason= registry name + date. - Audit.
GET /dnc?source=call_opt_outshows who asked during a call — proof of honouring requests.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

