LEND360 2026 runs October 12-14 at the Fairmont Austin in Austin, Texas. It is the annual online-lending summit for consumer and small-business lenders, service partners, investors, and banks evaluating fintech and new technology. If your lending team is attending, borrower communication is one of the operational areas most worth evaluating.
The Tells.co team will be there. Here is a practical framework for what to assess.
Borrower Communication Speed Is an Infrastructure Problem
When a borrower submits a loan inquiry, the interval between that submission and the first meaningful contact shapes whether the conversation continues. Lending teams that rely on email-only follow-up or manual call queues should review who owns the response queue and what happens outside staffed hours.
SMS and RCS are faster channels for mobile-first borrowers. The infrastructure question is whether your current stack can trigger a permission-based message the moment a lead is captured, through your own CRM workflows and API events, and then hand the conversation to a human when the context calls for it.
Permission Is the Starting Point, Not an Add-On
Every borrower communication program is only as strong as the consent that underpins it. Lenders operate under specific regulatory requirements for consumer communication. Permission-based messaging is not just a compliance safeguard. Respecting permission and recipient preferences supports a more trustworthy customer experience.
When evaluating messaging tools at LEND360, ask three questions:
- Does the platform enforce explicit opt-in before any send?
- Can you build SMS and RCS cadences that respect borrower consent and preferences?
- Does the platform handle channel fallback so that an RCS message that cannot be delivered falls back to SMS without losing the thread?
RCS gives lenders access to richer messaging than plain SMS: branded sender identity, inline media, and interactive elements. SMS is an important channel for time-sensitive notifications. A platform that supports both within a single permission-based framework gives the operator flexibility without fragmenting consent management.
AI Agents for Triage, Not Underwriting
The market is filling with AI tools that claim to handle borrower conversations autonomously. Lending teams should be specific about what AI agents can and cannot do in a regulated environment.
AI SMS and voice agents are useful for high-volume initial engagement and triage. They can handle the first response, route inquiries by type, and reduce manual burden during peak periods. They are not a replacement for human judgment in qualification, underwriting, or lending decisions.
When evaluating AI messaging tools, ask:
- Does the AI agent handle initial contact and triage, then hand off to a human for qualification and closing?
- Can your team define the boundary between AI-handled and human-handled interactions?
- Is the AI agent's behavior auditable within your CRM system of record?
Operator-Controlled Workflows, Not Platform-Imposed Sequences
Lending teams have existing loan management systems, CRM platforms, and compliance governance frameworks. A messaging tool that imposes its own cadence logic and handoff rules forces the lender to adapt to the tool rather than the other way around.
Tells.co offers SMS, RCS, REST API access, webhooks and CRM integrations. During a demo, evaluate how these capabilities fit your loan management system and which context and events can travel into your human handoff process.
The platform does not guarantee specific regulatory outcomes. Compliance with lending regulations, consumer protection rules, and messaging consent requirements remains the responsibility of the operator. Tells.co provides the infrastructure. The operator defines the governance.
Attribution and Auditability
Every send, response, and handoff is an event. If your messaging platform does not provide event-level data that feeds into your CRM and analytics systems, you cannot trace which message, which channel, and which handoff produced a conversation or a closed loan.
Tells.co provides webhooks and CRM integrations. Identify the specific available events, their reporting limitations and the work required to connect them to your own system of record.
What to Bring Back from LEND360
If your team is attending LEND360 2026, bring back three things:
- A clear assessment of how your current borrower follow-up speed compares to what SMS and RCS infrastructure could deliver.
- A specific plan for adding RCS to your permission-based cadence if you are not already using it.
- A defined handoff protocol that your team can implement, with triggers and context preservation specified.
To see how Tells.co handles permission-based SMS and RCS borrower communication with operator-controlled workflows, visit https://www.tells.co/start.
