--- title: "One-Page Contact Policy: A Playbook to Reduce Fatigue and Message Costs | Kilele Hub" description: "A practical template any engagement team can adapt—purpose tags, caps, suppression, quiet hours, and review rituals so outbound contact stays disciplined and defensible." url: "https://kilelehub.com/blog/one-page-contact-policy-playbook" published: "2026-07-05T00:00:00" updated: "2026-07-05T00:00:00" --- If you skim, read this - Tag every send: transactional, service, behavioral, marketing. - Publish caps, quiet hours, and suppression rules. - Review opt-outs and action decay monthly. Key takeaway If your contact rules do not fit on one page, frontline teams will not follow them—and customers will feel the gap. Strategy decks rarely stop three departments texting the same customer on the same day. A **one-page contact policy** does—if leadership backs it and tools enforce it. This playbook turns the ideas in [why you need a contact strategy](https://kilelehub.com/blog/why-you-need-a-contact-strategy-fatigue-reactance-costs) into something you can paste into Notion, share with vendors, and use in [Pulse](https://kilelehub.com/pulse) discovery workshops. ### Section 1 — Scope and principles - **Who this covers:** all outbound SMS, email, WhatsApp (and push if applicable) to customers, clients, members, or citizens. - **Principle 1:** every message has **one primary purpose** and **one primary action**. - **Principle 2:** **fewer, clearer** messages beat volume when action is the goal. - **Principle 3:** opt-out and quiet hours are **non-negotiable**. - **Principle 4:** exceptions require **named approver** + reason logged. ### Section 2 — Message purpose tags (use in your ESP/CRM) Train teams to tag every send: - **Transactional** — receipt, OTP, password reset, payment confirmed. Highest priority; minimal frequency debate. - **Service** — appointment change, delivery update, program deadline official notice. - **Behavioral** — reminder tied to a journey step (pay, upload, enroll, return). Must link to trigger + suppression rules. - **Marketing / growth** — promo, upsell, newsletter. Lowest priority; strictest caps. If two tags apply, **use the higher-priority rules** (transactional wins) or split into two messages on appropriate channels—not one overloaded SMS. ### Section 3 — Frequency and cooling-off (defaults to customize) Set defaults; tune with [experiments](https://kilelehub.com/blog/why-experimentation-beats-guessing-in-customer-communication): - **Marketing SMS:** e.g. max 2–4 per month per user unless they opted into more. - **Behavioral reminders:** e.g. max 2–3 per journey episode, spaced 24+ hours; **stop** after action or after cap. - **Cross-channel:** e.g. do not send the same CTA on SMS and email within 6 hours unless transactional. - **Cooling-off:** if two behavioral reminders ignored, **pause 7 days** and review barrier via Pulse—not a third ping the same day. Document: "We disclose frequency at opt-in" where regulations require it. ### Section 4 — Suppression list (always exclude) - Opted out (STOP honored immediately). - Journey complete (paid, enrolled, KYC done). - Active on another high-priority journey (define precedence). - Invalid / unreachable number (clean regularly—**save cost**). - Quiet hours (define local window; e.g. no promotional SMS 21:00–08:00 recipient time). ### Section 5 — Content and reactance-aware tone - Line one: **who, what action, by when** (amount, date, link). - No false urgency; rotate framing if repeating. - Offer **easy opt-out** and help path (short code, helpline). - Public programs: official sender, proportional language—see [AI drafting for public programs](https://kilelehub.com/blog/ai-drafting-trusted-public-outreach). ### Section 6 — Metrics and monthly review (30 minutes) Track per journey: - **Primary action rate** (not delivery alone). - **Opt-out / STOP rate** per 1,000 sends. - **Complaints** (support, social, helpline). - **Cost per completed action** (SMS spend ÷ primary actions). - **Fatigue signals** — declining action on same template over weeks. Agenda: What did we expect? What happened? Fatigue or reactance likely? Scale, change cadence, or [return to diagnosis](https://kilelehub.com/pulse)? ### Section 7 — Roles - **Journey owner** — caps, triggers, readouts. - **Data owner** — suppression, list hygiene, dashboards. - **Approver** — exceptions, public/regulated copy. - **Pulse partner (optional)** — barrier review when metrics stall despite policy compliance. ### How Kilele helps without replacing your policy **Pulse** stress-tests whether your policy matches real barriers—maybe the issue is trust, not frequency. **Hub** encodes triggers and exits when trials fit your stack. **AI** drafts messages **inside** your rules—not around them. **Enablement** gets Sender ID and channels live so policy applies to **trusted** sends—see [SMS setup types](https://kilelehub.com/blog/sms-channel-setup-types-for-kenyan-businesses). ### Copy-paste checklist before any campaign send - Purpose tag assigned? - Suppression applied? - Under frequency cap? - Quiet hours respected? - One primary action and working link tested? - Owner named for readout in two weeks? Download the habit, not more software: **one page, one review, one metric.** [Contact us](https://kilelehub.com/contact) to align a policy with Pulse discovery or [Hub waitlist](https://kilelehub.com/contact?intent=hub-waitlist) when execution is next. ## Continue the conversation See what we are testing in Labs, book Pulse discovery to design your test, or join Hub trial cohorts when you are ready to measure action—not delivery alone. [Pulse testing & diagnosis](https://kilelehub.com/contact?intent=pulse) [Hub trial testing](https://kilelehub.com/hub#hub-trial-launch) [Explore Labs](https://kilelehub.com/labs) [More insights](https://kilelehub.com/blog) ## Related reading in Customer Communication - [Customer Communication SMS vs WhatsApp for Customer Engagement in Kenya: Match the Channel to the Behavior Most teams pick messaging channels based on features they like. Better approach: map the channel to the specific behavior you need to trigger. 5](https://kilelehub.com/blog/sms-vs-whatsapp-for-customer-engagement-in-kenya-match-the-channel-to-the-behavior) - [Customer Communication WhatsApp Business Setup: Reach Customers Where They Chat—Without a Second Job WhatsApp is where many Kenyans expect replies—but verification, templates, and session rules are a project of their own. Enablement plus Kilele AI keeps your team on core work. 6 min read](https://kilelehub.com/blog/whatsapp-business-setup-stay-focused-on-core-work) - [Customer Communication Email Setup for Growing Teams: Deliverability Without the Distraction Email still matters for statements, onboarding, and formal updates—but SPF, domains, and bounce handling pull teams off core work. Enablement helps you send with confidence. 5 min read](https://kilelehub.com/blog/email-communication-setup-for-growing-teams)