Bring maintenance customers back.
Use past service dates to start the next tune-up conversation before the busy season.
An AI agent designed to bring maintenance customers back, revisit open estimates, and keep service inquiries moving. More jobs from the customer list you already have.
Seasonal service is due. No open appointment. Customer prefers a morning callback.
Hi Alex, I’m Riley, Oak & Air’s virtual assistant. We helped with your AC last year. Are you thinking about a tune-up before the weather warms up? I can have the office reach out.
I’ll ask the office to call tomorrow morning. Is this still for the system we serviced last year?
Interested in a tune-up. Office callback requested.
In this home services example, the agent has a reason to reach out, a next step to pursue, and a record to carry forward.
Check service history and avoid contacting someone already booked.
Confirm what is needed and send a useful callback brief to the office.
Use the completed service record to time the next maintenance conversation.
Make time for the customers who need a reminder, an answer, or a callback.
Use past service dates to start the next tune-up conversation before the busy season.
Find out whether the work is still needed and get interested homeowners back to the office.
Reconnect with people who asked for service but never got on the schedule.
Tell us where conversations stall and which systems hold your customer history. We’ll review the fit and map a first use case: the audience, the agent’s job, and the result worth measuring.
Your next step is a conversation about scope, connections, channels, and pricing. No customer outreach starts from this form.
That is the point: define the work you want handled, rather than build another set of campaigns. The first conversation maps what the agent should own and where your people should step in.
A reminder fires on a schedule. The Rekindle vision is to use the customer’s history and reply to decide what happens next: answer, follow up later, arrange the next step, or bring in your team. We map the required channels and connections for your use case before agreeing a deployment.
Tell us which CRM you use. We’ll assess its available data and connection options, including exports, before proposing a first deployment. Your existing system remains the source of customer history.
Request an agent plan to discuss one concrete use case. Scope and pricing depend on the workflow, data sources, channels, and volume. You review the proposal before committing.
We design the handoff around your team: who should respond, what context they need, and what the agent must not decide. Pricing, clinical advice, and other judgment calls stay with the right person.