Use the inquiry and client offer as the starting point.
Keep the next conversation from slipping away.
Follow-Up Assistant is designed to prepare relevant email and SMS drafts from the original inquiry, the client's offer, and the rules your team sets.

Keep the next action assigned and reviewable.
Preserve replies and outcomes on the same record.
Make the next message feel connected to the first one.
Follow-up works better when timing, context, ownership, and approval are treated as one workflow.
Start from what the lead already told you.
Prepare a draft using the original question, service interest, timing, and prior conversation instead of a generic sequence.
- Carry forward the original inquiry
- Keep the client's offer in view
- Avoid asking for details already provided
Keep client voice and judgment in the loop.
Give the owner a clear place to review, edit, approve, or take over before a message is sent.
- Make the owner visible
- Separate draft from send
- Keep edits with the activity history
Know what should happen after the reply.
Connect responses to a callback, qualification step, appointment, or closed loop so the team can see where the conversation stands.
- Attach a clear next action
- Route replies to the right owner
- Keep the outcome visible
From inquiry to an owned follow-up.
The workflow keeps a person in control while removing the need to reconstruct context for every message.
- 01
Inquiry captured
The lead, source, question, and conversation enter one record.
- 02
Draft prepared
Client context and follow-up rules shape a proposed response.
- 03
Owner reviews
A person can approve, edit, reassign, or take over.
- 04
Outcome stays visible
The reply and next action remain connected to the lead.
For teams where timely, thoughtful follow-up matters.
Lead response teams
Keep new inquiries moving without relying on personal reminders.
Account managers
Review drafts in the context of the client and conversation.
Appointment teams
Carry service, timing, and contact details into the booking workflow.
Know what the experience requires before you plan around it.
These answers separate the frontend experience from the phone, messaging, calendar, data, and publishing connections it may require.
Does the assistant send messages without review?
The interface is designed to support review and takeover points. Sending behavior should follow the permissions and automation rules configured for the account.
Can it use both email and SMS?
The page describes a channel-aware workflow. Actual sending depends on the email and messaging providers connected to the account.
Can each client have a different voice?
Client-specific offers, language guidance, and approval rules are intended to live in that client's workspace.
What happens when a lead replies?
The reply should return to the connected conversation so the owner can see the history and choose the next action.
Keep every follow-up connected to the reason it matters.
Map your current response and approval process with the Marrova team.