History-aware replies
For eligible conversations, LoanWick retrieves available Bonzo history and waits when required history checks are incomplete. Large-book onboarding runs in the background.
Reply to leads, follow up, coordinate appointments and keep Bonzo up to date. LoanWick uses available conversation history and your team’s rules, with company and loan-officer controls.
A good reply depends on more than the last message. LoanWick assembles the lead’s history, CRM notes, stage, assigned officer, and operating rules before it writes.
For eligible conversations, LoanWick retrieves available Bonzo history and waits when required history checks are incomplete. Large-book onboarding runs in the background.
Lead notes can explain why a conversation went cold, identify vintage leads, or record a prior request. The assistant uses that context to reopen thoughtfully instead of asking a generic “how can we help?”
Teams can review synced conversations and live activity from the dashboard, including the message history LoanWick is using and recent delivery or gating events.
An administrator can set a company default, then override it for an officer, a pipeline, or one stage. This makes mixed workflows possible without duplicating pipelines.
LoanWick can propose available times, share the right officer’s Calendly link, record appointment context, and keep the pipeline aligned with the scheduled conversation.
Each officer can set a timezone, daily availability and personal days off. Company closures still apply. External calendar free/busy availability is not synchronized.
Each loan officer can have separate Calendly and Loanzify links. Company defaults fill the gap when an officer leaves one blank.
Appointment state can be reflected in Bonzo with an internal note and configured stage movement, while the lead conversation remains available for the next handoff.
No AI system is perfect. LoanWick therefore places deterministic checks around the model and blocks risky conditions before the Bonzo delivery request.
Explicit STOP, remove, unsubscribe, and automated-list removal signals prevent future assistant messaging. Calling requires its own consent and do-not-call controls; a messaging opt-out is not permission to call.
Internal prompt markers, prompt fragments, and instruction-like output are rejected during generation and again at the final network boundary. A detected leak cannot be transmitted through the guarded send path.
Recent human activity, near-duplicate drafts, send claims, and active operations suppress overlapping messages and reduce double work.
Proactive messages are blocked from fabricating confirmed appointments or pretending a lead made a request that is not present in the conversation.
The platform can enforce the configured lead-local window within the federal ceiling and supported state-specific restrictions. Customers remain responsible for their legal configuration.
Gated sends, failed deliveries, stage movements, and automation work are logged so the team can diagnose what happened instead of guessing.
LoanWick provides automation controls intended to support a compliance program. It is not legal advice, does not independently determine every rule that may apply, and cannot guarantee zero violations. Review your setup with qualified counsel.
Officers can control the parts that should feel personal while administrators retain the controls that must stay consistent.