Services, hours, locations, policies, FAQs and process rules become usable context — not a generic settings list.
General
Your business.
Your lead process.
One connected system.
Configure LeadArivo around your services, hours and process — then keep every enquiry on one Next Step.
Website Chat
“Hi, I’d like to know more about your service. Can someone call me tomorrow afternoon?”
- Intent
- Service enquiry
- Requested action
- Contact requested
- Preferred timing
- Tomorrow afternoon
Illustrative LeadArivo workspace. Sample enquiry; not a customer record.
Built around your business
Your business does not need to fit a template.
General gives businesses a flexible LeadArivo setup shaped around their own services, policies, operating rules and lead journey.
- ServicesWhat the business offers
- HoursWhen the team can respond
- LocationsWhere work is handled
- PoliciesHow the business operates
- FAQsConfigured answers
- Process rulesCall-back and follow-up
LeadArivo Core + Business Knowledge + lead context + configured process.
End-to-end lead journey
One enquiry. One connected journey.
LeadArivo is built around what happens after the enquiry arrives — through context, Next Step, team follow-up and a recorded business outcome.
“Hi, I’d like to know more about your service. Can someone call me tomorrow afternoon?”
- Leads
- Conversations
- Activity
- Follow-ups
- Outcomes
Nikhil Rao Hi, I’d like to know more about your service. Can someone call me tomorrow afternoon?
The same lead stays in view. Contact is the person. Conversation, follow-up and outcome remain attached.
Understand what the lead wants
Know what they want before you act.
A raw enquiry becomes useful context. Fields shown here are an illustrative demonstration — not every field is always extracted automatically.
“Hi, I’d like to know more about your service. Can someone call me tomorrow afternoon?”
Useful context
Business Knowledge
Your business knowledge gives every enquiry context.
Configured information about how the business actually works helps Lead Guidance decide the next action — without pretending LeadArivo can see live inventory or employee calendars.
“Can someone contact me tomorrow afternoon?”
Hours, services, location, policy and process rules make that request usable. LeadArivo still needs a person to make the call.
- HoursBusiness is open tomorrow afternoon
- ServicesA relevant service exists on file
- LocationsA contact location / branch is configured
- PoliciesA contact / call-back policy applies
- Process rulesRequested timing can be used for follow-up
- FAQsConfigured contact information can support the reply
These are configured business facts — not live staff availability, inventory, ERP or payment state.
One lead → one Next Step
Lead Guidance publishes one current action.
LeadArivo Core stays the same. Business Knowledge, configured rules and Product Mind contribute. Lead Guidance determines the Next Step.
Contact the lead tomorrow afternoon
- What
- Contact lead
- Why
- The person explicitly requested contact
- When
- Tomorrow afternoon
Assignee Priya Shah remains responsible. There is one current action — not a list of equal recommendations.
Automation + team continuity
Automate the repeatable. Keep your team close.
Supported actions can run where capability and rules allow. When a person must contact the lead, the enquiry stays in view.
- TriggerNew website enquiry
- Context / conditionsHours, process rule, assignment state
- Supported actionAssign · create follow-up · notify the team
- Activity recordedThe same lead keeps the history
If a supported action cannot run, a person still has what they need.
- Assign the lead
- Create a follow-up
- Notify the team
- Contact remains known
- Conversation stays visible
- Assignee stays clear
- Next Step stays clear
- Follow-up stays connected
- Activity stays recorded
Keep the whole lead story connected
See the whole lead before you act.
Your team should not have to reconstruct an enquiry from disconnected tools before deciding what to do next.
Conversations
Nikhil Rao Hi, I’d like to know more about your service. Can someone call me tomorrow afternoon?
The same LeadArivo workspace remains. Only the focused area changes. LeadArivo is not a helpdesk or support-ticket system.
Source stays attached
Keep the original lead source attached.
Website, chat, ads, email and referrals can be recorded as origin. That does not make them native LeadArivo Connect integrations.
- Build in LeadArivo
- Lead Form
- Embed on website
- Visitor submits enquiry
- Lead enters LeadArivo
The Lead Form becomes part of the same connected journey — a native capture experience, not a separate form product.
- Configure in LeadArivo
- AI Chat
- Embed on website
- Visitor conversation
- Context + lead
- Same LeadArivo journey
AI Chat is a LeadArivo-native capture and conversation experience. It is not a standalone chatbot product.
Source, capture method, communication channel and action capability are not the same thing. Names shown here are origin and attribution — not a catalogue of native integrations.
LeadArivo Core
See the lead. See the context. Know what happens next.
See the contact, the original source, the requested call, the Assignee and the one current Next Step in the same LeadArivo workspace.
Nikhil Rao Hi, I’d like to know more about your service. Can someone call me tomorrow afternoon?
Leads by Source · Website remains attached

