How RK Drives Engagement
Micro-conversations, long-horizon nurturing, and cross-channel consistency powered by your knowledge library
What It Is
The Reusable Knowledge Base is not just a reference library that SI checks occasionally. As of the April 2026 SI update, every RK item is fully embedded in every SI processing pass. This means that every time SI decides to engage a contact — whether by email, SMS, Phona call, or live chat — it has your complete knowledge library available as raw material.
This changes what SI can do. Instead of relying on the brand voice and contact data alone, SI can now autonomously construct micro-conversations — short, purposeful exchanges built from your Talking Points, Objections, Rapport Questions, FAQs, and Conversation Starters. Each micro-conversation addresses one specific angle, keeps the message concise, and creates a natural reason for the contact to respond.
The result is engagement that does not sound automated, does not repeat itself, and does not run out of things to say — because the RK library gives SI a continuously available pool of substantive material to draw from.
Why It Matters
The fundamental problem with automated engagement is exhaustion. A 6-email drip sequence runs out in two weeks. Even a sophisticated workflow with branching logic eventually reaches the end of its content. After that, the contact either converts or goes silent — and the system has nothing left to say.
RK-powered SI does not have this limitation. With 40 items across five types (the default starting point), SI has dozens of angles to work with. It can lead with a Talking Point in one email, follow up with a Rapport Question in the next, address a preemptive Objection in the third, and share a Conversation Starter in the fourth — each one different, each one substantive, and each one selected based on what SI knows about this specific contact's engagement history.
This is particularly powerful for three scenarios:
Long sales cycles. When a prospect takes 6-12 months to decide, template sequences run dry in week two. SI with RK maintains meaningful engagement for the entire cycle, drawing from different item types to keep conversations fresh.
Re-engagement of dormant contacts. When a contact goes quiet, SI uses Conversation Starters and contextual Rapport Questions to restart dialogue without the dreaded "just checking in" message.
Multi-channel consistency. When a contact interacts via email, then chat, then phone, SI draws from the same RK library across all channels. The Talking Points referenced in an email are consistent with what Phona says on a call and what Live Chat answers in a conversation.
How It Works
The SI Processing Pass
Every time SI evaluates whether and how to engage a contact, it runs a processing pass that loads:
1. The contact's full profile (engagement history, stage, segment, custom fields)
2. The brand definition (voice, narrative, persona)
3. All active mandates matching the contact's context
4. The complete RK library (filtered by product scope and persona scope relevance)
SI then decides: What is the right message for this contact right now? It selects from the RK based on:
- What has already been used — SI tracks which RK items have been referenced in previous communications with this contact and avoids repeating them
- What matches the contact's current state — A contact who just visited the pricing page might trigger an Objection about pricing; a contact who has been quiet for 30 days might trigger a Conversation Starter
- What severity applies — High-severity items are prioritized when multiple items could fit
- What product scope matches — If the contact is interested in a specific ware, product-scoped items take priority over brand-wide ones
Micro-Conversations
A micro-conversation is a single exchange — one message with one purpose — designed to elicit a response. Instead of sending a long email covering three talking points, SI sends a short message built from one RK item. This approach is:
- More likely to be read (shorter messages get higher engagement)
- More likely to get a reply (focused questions get more responses than generic updates)
- More sustainable over time (one RK item per touchpoint means 40 items = 40 unique touchpoints)
Cross-Channel Application
RK items are channel-agnostic in their content but channel-adapted in their delivery:
- Email — SI composes full messages drawing from Talking Points, Objections, or Conversation Starters
- SMS — SI condenses the RK item into a short, conversational text
- Phona — The voice AI references FAQs, Rapport Questions, and Objections during live calls
- Live Chat — Instant responses powered by FAQs and Talking Points, with Rapport Questions for deepening conversations
Examples
A coaching prospect has been in the pipeline for 3 months with declining engagement
SI has already used the main Talking Points and product features in earlier emails. For this month's touchpoint, SI selects a Conversation Starter: "We just surveyed 200 coaches about their biggest time sink — curious if yours matches the top answer." This is not a sales pitch. It is an invitation to engage that references something relevant to their world. The contact replies, re-opening the conversation.
A realtor prospect visits the pricing page then goes quiet for a week
SI detects the pricing page visit and the subsequent silence. It pulls a pricing Objection from the RK ("Price Sensitivity") and a Talking Point about ROI from the realtor segment. It composes an email that addresses the likely hesitation directly: acknowledges that the investment feels significant, references how other realtors recovered the cost within the first quarter through saved time, and suggests a brief call to walk through the numbers.
A contact asks about integrations in Live Chat, then gets a follow-up email from SI the next day
During the chat, Live Chat references the "What integrations do you support?" FAQ from the RK. The next day, SI composes a follow-up email that builds on the chat — it does not repeat the FAQ answer but instead selects a Talking Point about how native integration through a single platform eliminates the data fragmentation the contact was asking about. The RK provides consistent information across channels while SI ensures the conversation progresses rather than circles.
