> ## Documentation Index > Fetch the complete documentation index at: https://docs.orbit.devotel.io/llms.txt > Use this file to discover all available pages before exploring further. # UK Ofcom Dropped-Call Posture > Ofcom's dropped-call policy for predictive dialler campaigns into UK numbers — the 3 % live-answer ceiling per dialling period, the two-attempt recording-consent rule, and six-month recording retention — mapped onto the tenant-owned Orbit controls that evidence each obligation. # UK Ofcom Dropped-Call Posture When your predictive dialler abandons an answered call into a UK number — the recipient picked up but no agent was connected within the connect window — the posture you answer to is Ofcom's dropped-call policy, not the FCC's abandoned-call safe harbor. This page maps Ofcom's three obligations onto the same tenant-owned controls the [FCC safe-harbor page](/compliance/dialer-abandoned-call-safe-harbor) documents for US calls, and adds the two steps only the UK regime demands: recording consent across re-attempts, and six-month recording retention. This page documents tenant-owned configuration. It is **not legal advice**, and Devotel Orbit does not guarantee your compliance — the controls are tenant-owned, and whether your operations stay inside the safe harbor is your responsibility. Confirm your posture with qualified counsel. ## Why UK abandoned calls are a separate regime The [FCC page](/compliance/dialer-abandoned-call-safe-harbor) covers 47 C.F.R. § 64.1200(a)(7): a 3 % ceiling measured per campaign over a 30-day window, plus a prerecorded identification message — business name and toll-free do-not-call number — played into the abandoned leg before the two-second disconnect. Ofcom's dropped-call policy is a different rulebook: | Obligation | Ofcom dropped-call policy | FCC § 64.1200(a)(7) | | - | - | - | | Abandon ceiling | 3 % of calls answered by a live person, per dialling period | 3 % per campaign over a 30-day rolling window | | Abandoned-leg handling | Recording-consent exposure counted across two attempts | Prerecorded business name + toll-free do-not-call number, two-second disconnect | | Evidence retention | Recordings kept for six months | No retention obligation | The two regimes are not interchangeable. A campaign configured only for the FCC path plays a US-style identification message into UK abandoned legs and retains nothing for the six-month window — and the FCC page's 30-day measurement window does not bound Ofcom's per-dialling-period ceiling. If you dial UK numbers with a predictive dialler, treat this page as the controlling posture and the FCC page as the US supplement. ## Tenant-owned posture The controls this page maps share the FCC page's provenance: * **Per-campaign abandon ceiling.** `max_abandon_rate` carries a hard 0.03 maximum you cannot raise, and pacing throttles as the rolling rate approaches it, auto-pausing the campaign when the ceiling trips. The same 0.03 ceiling is your starting position for Ofcom's 3 % live-answer cap; because the measurement windows differ (dialling period versus 30-day window), a campaign sitting at the ceiling is inside the US rule, but you should still watch the per-period rate for the UK one. * **Per-campaign safe-harbor object.** `metadata.safe_harbor`, set on create or update through the campaign endpoints, supplies what the abandoned leg hears, with organization-level fallback for the business name and the opt-out line. * **Recording controls.** The campaign's recording flag, together with your organization's consent-announcement mode, decides which calls are captured and what each party hears before capture. Map those onto Ofcom's two recording obligations: * **Two-attempt recording consent.** Pair the abandoned-leg announcement with your consent announcement so a recipient whose dropped call carried a recording notice was told recording happens; then shape re-attempts — the campaign retry schedule is tenant-owned metadata as well — so a recipient exposed to the consent recording on a dropped call is not re-exposed beyond the policy's two-attempt allowance. * **Six-month recording retention.** Orbit's retention window (**Settings → Compliance → Retention**) auto-deletes recordings; the Ofcom obligation runs the other way. Route recorded calls through archival export so the dropped-call evidence set survives the auto-delete window for at least six months. ## Configure for Ofcom 1. **Keep the ceiling at or below 0.03.** The platform enforces the maximum; set a lower per-campaign value if your dialling periods concentrate volume. 2. **Opt in the safe-harbor object.** On `POST /api/v1/dialer/campaigns` (or `PATCH /api/v1/dialer/campaigns/:id`), add `metadata.safe_harbor` with a UK-appropriate message — presence of the object enables it, exactly as on the FCC page. 3. **Announce recording consent to every party.** Set the consent-announcement mode to `announce_all` so every recorded leg plays the consent announcement to all parties, as [recording consent](/compliance/recording-consent) requires for two-party-consent jurisdictions. 4. **Retain the evidence for six months.** Connect an [archival export](/compliance/archival-export) for recorded calls and keep dropped-call recordings at least six months, outside the auto-delete window. 5. **Bind the evidence.** Export the abandoned-call evidence set with the [evidence binder](/compliance/evidence-binder): the `dialer_call_abandoned` and `dialer_safe_harbor_message` events, plus the retained recordings, form the dropped-call audit. ## Worked example: safe\_harbor tuned for UK recordings ```json theme={null} { "metadata": { "safe_harbor": { "enabled": true, "business_name": "Acme Home Services UK Ltd", "opt_out_number": "+448005551212", "message": "This call was made on behalf of Acme Home Services UK Ltd and may be recorded. We are sorry we are unable to connect you with a representative at this time. To be placed on our do-not-call list, please call 0800 555 1212." } } } ``` With the campaign's recording enabled and the consent-announcement mode set to `announce_all`, an abandoned UK leg hears the identification and the recording notice before disconnect, and the recording of that leg flows to your archival export for the six-month window. Verify with the same events as the FCC page: `dialer_safe_harbor_message` on each abandoned leg, and a flat `dialer_safe_harbor_unconfigured` count. Dialer campaign console: abandon-rate gauge reading 1.8 % against the 3 % ceiling, with pacing state and the auto-pause threshold The 0.03 ceiling guard throttles pacing, but it does not substitute for the recording-consent announcement or the six-month retention — all three obligations must hold for a defensible UK dropped-call posture. ## See also * [Dialer Abandoned-Call Safe Harbor](/compliance/dialer-abandoned-call-safe-harbor) — the FCC § 64.1200(a)(7) twin of this page * [UK PECR / ePrivacy](/compliance/uk-pecr-eprivacy) — the sender-rule regime for UK marketing calls and messages * [Recording consent](/compliance/recording-consent) — the `announce_all` consent-announcement axis * [State calling windows](/compliance/state-calling-windows) — dialing-window rules for US campaigns * [Archival export](/compliance/archival-export) — long-retention export for recordings * [Evidence binder](/compliance/evidence-binder) — exporting the compliance evidence set This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.