# OPS-108 — A do-not-call request is recorded when it is made

> A do-not-call request must be recorded, with the name and number, at the time the request is made.

- **Rule ID:** OPS-108
- **Layer:** Operational (`OPERATIONAL`)
- **Checks:** `internal do-not-call write latency`
- **Severity:** BLOCKING — Breaking this rule gets the submission rejected outright.
- **When it bites:** Falls due after approval, once you are live and sending
- **How it is detected:** Not knowable before submission — reported with its deadline
- **Fix type:** Wait on an external system or a required interval
- **Required by:** FCC
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/operational/ops-108/

## Why this rule exists

The obligation is about latency rather than storage: a request written up at the end of the week is a week in which the number can still be messaged, and the record then shows a delay nobody can explain. It is also the moment the identifying detail is available — the person is on the phone — and reconstructing a name from a number afterwards is exactly what does not happen.

## How to fix it

Make the request recordable during the contact — a field the agent sets before ending the call, not a form filed later — and write the name and number together. Done when the record timestamp matches the contact timestamp.

## Example of a compliant value

```text
Agent sets Do Not Call on the account during the call: name, number, request received 2026-03-04T11:02Z.
```

## Check this yourself

**Does the record timestamp on a do-not-call request match the contact timestamp?**

1. Trace the workflow: is anyone asked to enter these after the fact? Batch entry at the end of a shift is common and it is what creates the latency.
2. Make the request recordable during the contact — a field the agent sets before ending the call — and capture the name and number together.

*What wrong looks like:* A request written up at the end of the week is a week in which the number can still be messaged. The name is available while the person is on the phone and is never reconstructed afterwards.

## Notes

A workflow inside the brand. What the user has to check is whether their process asks anybody to do this after the fact; batch entry at the end of a shift is common and it is what creates the latency this rule is about.