--- title: "Why You Need a Contact Strategy: Beat Fatigue, Reactance, and Wasted Sends | Kilele Hub" description: "More messages rarely mean more action. A contact strategy sets who you reach, when, on which channel, and why—so engagement stays trusted, measurable, and cost-aware. Here is how behavioral science and Pulse fit in." url: "https://kilelehub.com/blog/why-you-need-a-contact-strategy-fatigue-reactance-costs" published: "2026-07-02T00:00:00" updated: "2026-07-02T00:00:00" --- If you skim, read this - Fatigue = too many similar messages; people tune out or push back. - Reactance = autonomy threatened; people do the opposite of your ask. - Strategy = purpose, caps, triggers, suppression, one owner. Key takeaway Without a contact strategy, teams default to volume—and volume drives fatigue, reactance, opt-outs, and SMS bills that do not move your primary metric. If you engage customers, clients, members, or citizens by SMS, email, WhatsApp, or push, you have felt the tension: leadership wants **more outreach**; operations sees **rising costs and complaints**; customers stop responding altogether. That is not a copy problem alone. It is often a **contact strategy** problem—no shared rules for who gets what, when, and why. Research on **message fatigue** describes a state where people feel they have received **too many similar messages** and become exhausted, bored, or resistant. Meta-analytic work links higher fatigue to **unintended outcomes**—weaker persuasion and even movement **away** from the behavior you wanted. Repetition without relevance does not build habit; it builds noise. **Psychological reactance** adds another layer: when people feel pressured or that their freedom to choose is threatened, they may **resist on purpose**—ignore, opt out, or act opposite to the nudge (sometimes called a boomerang effect). Heavy urgency, command-like tone, and relentless reminders are common triggers—especially on a personal channel like SMS. For any organization, the cost is real in three currencies: **trust**, **attention**, and **money** (per-segment SMS fees, duplicated cross-channel sends, staff time answering "stop messaging me"). A contact strategy is how you protect all three while still moving people to act. ### What a contact strategy is (plain definition) A **contact strategy** is a written, shared set of decisions about: - **Purpose** — why this message exists (transactional update, behavioral reminder, service notice, marketing). - **Audience** — who qualifies and who must be **suppressed** (already paid, already enrolled, opted out, in quiet hours). - **Channel** — SMS vs email vs WhatsApp vs agent call—not **every channel at once** with the same text. - **Cadence** — max touches per journey per week; cooling-off after no response. - **Content rules** — one primary action; no fake "last chance" every day. - **Governance** — who approves exceptions; how you measure harm (opt-outs, complaints, action decay). It is not a brand book. It is **operating policy** for outbound contact—so product, marketing, collections, and program teams stop working at cross purposes. ### How fatigue and reactance show up in your data Watch for early warnings **before** list health collapses: - **Flat or falling action rate** while delivery stays high—see [when SMS delivers but action stays flat](https://kilelehub.com/blog/when-sms-delivers-but-action-stays-flat). - **Rising opt-outs and STOP replies** after a campaign burst. - **Support or helpline spikes** ("Is this a scam?" "Why three texts today?"). - **Shorter time-to-ignore** on repeat journeys—same cohort, weaker results each wave. - **Cross-channel duplication**—email, SMS, and push with identical CTAs within hours (feels like surveillance, not service). Fatigue often **mediates** reactance: people first tune out, then actively resist. Treat rising fatigue as a **stop signal**, not a cue to send louder. ### Design principles that reduce fatigue and reactance ### 1. Behavior-triggered beats calendar-blind Send when an event shows someone is **ready, stuck, or at risk**—payment due in 48 hours with no attempt, onboarding step idle 24 hours—not because Tuesday is newsletter day. See [automation that respects behavior](https://kilelehub.com/blog/automation-that-respects-behavior-not-spam). ### 2. One journey owner, one primary metric If collections, marketing, and product each run separate SMS streams to the same person, **no single team sees overload**. Assign journey ownership and a shared suppression list. ### 3. Frequency caps and cooling-off periods Static caps (e.g. "max two SMS per week") are a floor, not a ceiling—segment by risk and intent. High-intent transactional messages differ from promotional nudges. After two ignored reminders, **pause** and diagnose before a third ping the same afternoon. ### 4. Respect autonomy in wording Clear information, easy opt-out, proportional tone. Explain **what happens if they act and if they do not**—especially for public programs. Reduces reactance compared to vague threats or manipulative urgency. ### 5. Channel fit, not channel carpet-bombing SMS for time-sensitive, short actions; email for detail; WhatsApp where conversational context helps. Copy-pasting the same paragraph everywhere trains people to ignore **all** of it. ### 6. Suppression rules (non-negotiable) Exclude: paid, completed, enrolled, opted out, recently contacted on another journey, wrong time zone / quiet hours. **Failed sends still cost money** on many gateways—fix lists before scale. ### 7. Test cadence like you test copy Cadence is a lever. In [A/B tests](https://kilelehub.com/blog/ab-testing-sms-what-to-test-and-how-to-measure), hold message constant and vary timing—or hold timing and vary frequency for a defined cohort—with **action rate** as primary metric. ### Where Pulse, Hub, and analytics fit **Analytics** shows leaks and decay: funnel drops, cohort fatigue, segment differences. **[Behavioral data science](https://kilelehub.com/blog/what-is-behavioral-data-science-a-practical-introduction)** asks *why*—salience, friction, trust, timing, reactance to tone. **[Kilele Pulse](https://kilelehub.com/pulse)** is the right door when: - Action fell but sends increased. - Teams debate "send more" vs "customers are angry." - You need a **barrier map** and testable levers—not another creative brainstorm. Pulse helps you name whether the problem is **message content**, **cadence**, **channel mix**, or **product/process** mismatch—and prioritize one experiment. **[Kilele Hub](https://kilelehub.com/hub)** (as trials open) executes journeys with variants, triggers, and reporting tied to **action**, not delivery—encoding caps and exit rules when someone pays or completes a step. **[Kilele AI](https://kilelehub.com/ai)** can draft variants and summarize readouts; **humans** approve sends and set policy. AI should not override frequency rules you agreed in your contact strategy. ### Cost control without starving revenue A good strategy **cuts waste**, not all contact: - Fewer **redundant** segments (160-character discipline; avoid multi-part SMS when one line suffices). - Fewer **duplicate** journeys to the same user the same day. - More **triggered** high-intent messages (repayment window, cart abandon) vs unfocused blasts—often better ROI per shilling spent. - **List hygiene**—remove invalid numbers, honor STOP immediately, do not pay to message ghosts. Kenya-shaped nuance: airtime and trust matter. Unknown senders plus high frequency feel like **cost and risk** to the recipient, not service. ### Public and regulated programs Citizens react strongly to perceived **surveillance** or **punitive** tone. Program partners need contact rules oversight can explain: purpose, frequency disclosure, opt-out, data use. Pair with [ethical public SMS playbook](https://kilelehub.com/blog/program-partner-playbook-ethical-public-nudges). ### Start this quarter Pick **one journey** (repayment, onboarding, enrollment). Document current touches per user per week. Count opt-outs and support tickets for two weeks. Run one [Pulse-style review](https://kilelehub.com/contact): Is the barrier fatigue/reactance, or something else? Then write a **one-page contact policy**—see [how to build a one-page contact policy](https://kilelehub.com/blog/one-page-contact-policy-playbook). Related: [data-driven engagement culture](https://kilelehub.com/blog/data-driven-engagement-culture-of-experimentation) · [when analytics meets behavioral science](https://kilelehub.com/blog/when-analytics-meets-behavioral-science-for-engagement) · [Book Pulse discovery](https://kilelehub.com/contact) ## 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 Behavioral Science - [Behavioral Science Why Customers Stall: The Real Reasons Kenyans Stop Using an App Most drop-off isn't about losing interest. It's about data bundles running out mid-flow, unclear next steps, and forgotten value props that never stuck in the first place. 5](https://kilelehub.com/blog/why-customers-stall-the-real-reasons-kenyans-stop-using-an-app) - [Behavioral Science Appointment Reminders in Kenya: Why Generic Reminders Fail and Behavioral Ones Work No-shows happen when the future appointment feels distant and friction feels immediate. Behavioral reminders close that gap with commitment framing and social norms. 5](https://kilelehub.com/blog/appointment-reminders-in-kenya-why-generic-reminders-fail-and-behavioral-ones-wo) - [Behavioral Science How to Improve Fintech Onboarding Completion Rates in Kenya: A Behavioral Playbook Most Kenyan fintechs lose users between OTP and first action. Here's how to diagnose the real friction points and fix them with behavioral science. 5](https://kilelehub.com/blog/how-to-improve-fintech-onboarding-completion-rates-in-kenya-a-behavioral-playbook)