Company admin quickstart
Set up the team. Review the boundaries. Then activate deliberately.
LoanWick helps mortgage teams use Bonzo for AI-assisted replies, follow-up, appointment coordination, and configured notes and pipeline actions. This guide is for a company administrator. A company admin is not the same as the platform owner.
1. Open your workspace
If your company already has a workspace, use your invitation or log in. Do not create a duplicate company. If you are setting up a new company, start here and verify your email.
Creating a workspace does not charge your card, start a free sending trial, or turn on outreach. Activation approval is required, and billing and setup requirements still apply afterward.
2. Connect the right Bonzo account
Use guided setup to connect the company's authorized Bonzo account. Keep API credentials in the secure setup fields; never send them by email or in a support message.
Confirm that the company, pipelines, and officer seats are the ones you expect. An imported officer seat is not proof that the officer has joined or finished setup. For a large CRM, allow onboarding and history synchronization to finish, then review its status before enabling outreach.
3. Invite the people who should have access
Open team management, enter the person's email, and choose the appropriate role. Confirm that the officer is attached to the correct seat. Check the invitation status and use the available resend/recovery option if needed; do not share a teammate's password.
- Company admin: manages team access and company-level setup.
- Loan officer: uses their attached officer workspace and personal settings.
- Admin who also handles leads: use the account role switch to move between company administration and your own loan-officer view. Confirm the active view before making a change.
Invite only the people who should be on the team. An invitation by itself does not finish their onboarding or activate their outreach.
4. Set a small, clear operating scope
Review the selected pipelines and stages, company schedule, days off, officer readiness, and outreach controls. Allow only the places where your team wants the assistant to work.
In Model versions, choose the company default if you want a named release. New releases do not automatically move the team. An officer may follow your default or pin an available version within the account's tier, subject to company restrictions. The choice does not change the plan or its prices.
5. Test before real outreach
Use Test the bot with fictional details and representative scenarios: a new reply, "not now," scheduling, an opt-out, and a question that needs the officer. Check the actual output and handoff behavior. Previewing a conversation is not a real SMS send and is not proof that a Bonzo action completed.
Verify the officer's personal availability, meeting link, assigned leads, tone, and notification setup. Make sure the team knows who reviews live conversations and who handles support.
6. Review activation and billing separately
Complete the platform's activation review, required setup, and the authorized billing arrangement. Approval removes the activation hold; it does not turn outreach on or change billing by itself.
Only an authorized admin should enable live activity after checking the company and per-officer settings. Begin with a controlled scope and review the results before expanding. Do not enable a whole CRM just to test it.
7. Watch the first live activity
Review conversations, scheduled work, appointments, stopped/held leads, and the cost view. A hold may be a deliberate safeguard, not an error: for example, a pipeline that is not enabled for that officer. Do not bypass it just to make a count look cleaner.
If behavior looks wrong, pause the affected scope where available and contact support with the page name, time, and a redacted screenshot. Do not include borrower documents, passwords, API keys, or authentication links.
Before enabling outreach: your check-off
- Correct company connected; no duplicate workspace.
- Authorized officers invited, attached, and finished with setup.
- Eligible pipelines/stages and schedule reviewed.
- Personal hours, days off, and meeting links reviewed.
- Model choice and any company restrictions understood.
- Test scenarios reviewed; human handoff owner identified.
- Appropriate permissions, consent, policies, and disclosures reviewed by the company.
- Activation approval, billing, and required setup complete.
- Company and officer switches intentionally set by an authorized person.
- First-live review and support owner assigned.
Need help? Use Support in the portal or email info@ethanwood.org. For a guided walkthrough, book a time with Ethan.
Loan officer quickstart
Make the assistant yours, without losing the team's boundaries.
LoanWick supports your follow-up in Bonzo. It can help continue lead conversations, coordinate appointments, and keep notes and configured pipeline actions organized. You remain responsible for borrower guidance, decisions, and human follow-up.
1. Join your team
Open your company invitation and finish the sign-in steps. If you already have access, log in. Use the email your admin invited. If your officer seat is missing or incorrect, ask the admin to attach the right seat before continuing.
Do not create a separate company just to join your existing team. An invitation does not automatically activate outreach.
2. Open My bot setup
Confirm your name, officer details, and connected Bonzo seat. Set the assistant's style, response length, and available preferences. Choose settings that fit how your team wants to speak to leads.
Review any booking or application links carefully. Do not paste passwords or API keys into instructions. Company restrictions and shared safety rules still apply.
3. Set Your availability
Review the displayed timezone and the personal booking hours. Keep the company defaults if they fit, or customize the personal settings available to you. Check your days off and any company-wide blocked dates before saving.
Make sure your scheduling link is correct. Do not assume that entering a link automatically synchronizes every event on an external calendar. Test the intended booking path and ask your admin about the team's scheduling setup.
4. Choose how model updates affect you
Open Model versions. Your available choices depend on your account tier and company restrictions.
- Follow company default: use the default selected by your admin.
- Keep legacy setup: keep the previous routing rules. These rules can change; this is not a frozen version.
- Choose a named release: pin an available Mini, Essential, Pro, or Max version, such as Pro v1.
A later company-default change does not replace an explicit officer pin. Publishing a new version does not switch anyone automatically. Choosing a version does not change your billing plan or prices. A named release pins the primary engine and its version-specific tuning, not the whole application. Shared rules and provider failover still apply.
5. Test a few real-world situations using fictional details
In Test the bot, try a normal reply, a lead who is not ready, an appointment request, an opt-out, and a question you would want to handle personally. Review what it actually says. Tests are previews, not real outreach or proof of completed CRM actions.
If the answer sounds wrong, adjust the settings you control or ask your admin for help. Do not put actual borrower financial details into a public demo.
6. Confirm readiness with your admin
Your company must finish activation approval, billing, and required setup before live outreach can start. The appropriate company and officer settings also need to be enabled. Finishing your personal setup alone does not start outreach.
Ask who reviews the first conversations, how you will receive handoff alerts, and how to pause activity if something needs attention. If you use Telegram alerts, finish the portal's Telegram connection steps; do not assume the alerts are linked just because you opened a bot chat.
Your first-day checklist
- Correct company and officer seat.
- Personal details, style, and links checked.
- Availability and timezone reviewed.
- Model preference understood and saved only if needed.
- Sample conversations reviewed.
- Notifications connected and handoff responsibilities understood.
- Admin has confirmed live readiness and operating scope.
Need help? Use Support in the portal or email info@ethanwood.org. Include the page name, approximate time, and what you expected to happen. Never include passwords, API keys, authentication links, or borrower documents.
LoanWick FAQ
What is LoanWick?
LoanWick is an AI-powered assistant for mortgage teams that works with Bonzo to respond to leads, follow up on conversations, coordinate appointments, and keep notes and pipeline stages organized. It adapts to each loan officer's style while giving company administrators control over team access and outreach settings. With conversation history, safety checks, and human handoffs built into its workflows, LoanWick helps loan officers spend less time on repetitive follow-up and more time helping borrowers.
Does it replace Bonzo?
No. It works with the connected Bonzo account. Conversation context and configured workflow actions depend on that connection and the available CRM data.
Does it replace a loan officer?
No. It assists with conversation and coordination. Loan officers remain responsible for advice, rates, eligibility, disclosures, decisions, and situations requiring human judgment.
Can I try it without contacting a borrower?
Yes. The interactive demo uses sample lead context and preview responses. It does not send an SMS or change a Bonzo record. Stage, task, and note previews are illustrative. Use fictional information only.
You can also call the AI demo yourself at 949-468-7967. Do not give it borrower information. Carrier charges may apply. A demo call is not an activation of your company's calling workflow.
Do I need a demo call before I start?
No. You can create a workspace, verify your email, and begin guided setup. If your company already has a workspace, ask your admin for an invitation instead of creating a duplicate.
Does creating a workspace start outreach or charge me?
No. Signup does not start a free sending trial, charge your card, or enable outreach. Activation approval is required. Required setup and billing still apply afterward, and approval alone does not enable the outreach switches.
How do admins add loan officers?
Admins can invite teammates by email and assign the appropriate role. The officer must use the invited email, finish joining, and be attached to the correct officer seat. Imported CRM seats, invited users, completed onboarding, and active outreach are different states.
What if I'm both an admin and a loan officer?
Use the account role switch when your account has both roles and an attached officer seat. Company admin view is for team-level controls; loan officer view is for your own work and preferences. The platform-owner workspace is separate from company administration.
Can every officer use different availability?
Officers can review company defaults and customize the personal availability settings available to them. Company-wide blocked dates and other scheduling boundaries still matter. Review the displayed timezone and test the intended booking path. A pasted scheduling link does not establish that every external calendar event is synchronized.
What are Mini, Essential, Pro, and Max v1 or v2?
Mini, Essential, Pro, and Max name the model tiers. Each tier can have published releases numbered v1, v2, and so on. Initial v1 entries are available. Newer versions are available only after they are published and permitted for your account.
Company admins choose a default. Officers can follow it, keep legacy routing, or pin a published version available within their account tier, subject to company restrictions. Publication does not automatically switch users or change billing. Choosing a version is not a plan upgrade.
Is "Keep legacy setup" the same as pinning v1?
No. Legacy setup keeps the old mutable routing rules. A named release pins its primary engine and version-specific instruction tuning. It does not freeze the entire application, shared safety rules, or company instructions. Existing provider failover can use another engine.
Will it change every pipeline stage?
No. Pipeline and stage behavior depends on the enabled company and officer settings. Review the specific stage-update mode and operating boundaries. A preview of a proposed stage action is not evidence that the connected CRM action has completed.
Why is a lead held or stopped?
A hold may mean the pipeline is not enabled for that officer, setup or history synchronization is incomplete, a limit applies, or a contact/opt-out rule blocks outreach. Check the explanation before treating the hold as a defect. Do not bypass a safeguard just to clear a dashboard count.
How much does it cost?
Ask the company admin to review the current plan and billing terms for the account. Pricing follows your company’s current plan and billing terms. A free sending trial is not included. Model-version selections alone do not change the plan or message prices.
What does the yearly cost outlook include?
The outlook estimates message charges using recent eligible sending activity and the recorded message rate. Company admins see the company scope; loan officers see their own scope. It is an estimate, not an invoice or an all-in operating budget. Calling, taxes, Bonzo and other services, discounts, minimums, and contract-specific charges can be separate. Without enough usable history, an estimate may be unavailable rather than showing a misleading zero.
Is there a guarantee of more replies or booked meetings?
No. Results depend on the leads, configuration, timing, connected services, and human follow-through. The launch materials make no reply-rate, revenue, or appointment guarantee.
Does it guarantee legal compliance?
No. The product has safety checks and controls, but it does not replace the company's responsibilities for consent, disclosures, licensing, policies, legal review, and human oversight. AI output can be incomplete or wrong. Borrower-specific decisions and regulated communications need appropriate human review.
How do I get support?
Use Support in the portal or email info@ethanwood.org. Share the page name, approximate time, what happened, and a redacted screenshot if useful. Do not send passwords, API keys, authentication links, borrower records, or financial documents. A response-time commitment is not stated in these materials.