James CarterViewing request · 2 minutes ago
AI handling
Intelligent WhatsApp service workflows
WhatsApp AI Assistant for property teams.
Property work rarely stops because the office is busy. A tenant may need help with a repair, a landlord may want an update, an applicant may be ready to book a viewing and a supplier may need the right contact. The Proplix WhatsApp AI Assistant gives those conversations a structured first response, gathers the details your team actually needs and keeps the next action connected to the CRM.
Routine journeys can continue in the background while your team concentrates on inspections, negotiations, compliance reviews or portfolio work. When a conversation needs judgement, empathy or a decision, an authorised team member can take over immediately and carry on from the same message history.
- Linked WhatsApp Web
- Multi-account access
- Live human takeover
- Works in the background
- Secure audit history
P
Proplix Assistant ●Online
Hello. How can I help with your property enquiry today?
I need to arrange a visit for a rental property in Manchester.
I can collect the details now. Which date or time window works best?
Tuesday morning, please.
Type a message
Live conversations 12 active
Priya ShahNeeds help with a repair
WaitingOliver BrownStaff member joined
LiveDetailed capabilities
A controlled assistant, shared inbox and CRM workflow in one service layer
The module is designed around linked-device WhatsApp operation, permission-aware staff access and durable CRM processing. The tabs below explain what each area contributes to the day-to-day customer journey.
Linked WhatsApp Web
Connect an approved WhatsApp account through the normal linked-device QR process. The module retains an isolated session for each account and does not require a separate WhatsApp Business API number.
Multi-account team access
Operate more than one WhatsApp number with permission-scoped access. Staff see only the accounts and actions they are authorised to use, while the last selected account can remain available across refreshes.
Guided first-contact handling
Present clear options, recognise a verified customer route, collect the information needed for the next step and return the customer to a useful menu after a successful action.
Browser-independent processing
When the background worker is healthy, enabled verification and automated responses can continue even when every CRM user is logged out or the administrator browser is closed.
Appointments and callbacks
Collect preferred dates, times and reasons. Native callback tasks can be created directly; appointment journeys can be connected to the Proplix Appointments and Scheduling workflow agreed for your organisation.
Standard replies and guidance
Use controlled standard replies and relevant Help Centre links to answer common questions consistently, while keeping more complex matters available for a person to review.
Registered-mobile recognition
A unique active contact can be recognised from the registered mobile number. Unrecognised numbers can be guided into an email-verification journey before customer-specific options are exposed.
Support ticket creation
Collect a short subject and useful details, create the ticket through the native CRM model and avoid opening a duplicate WhatsApp ticket while an existing one is still awaiting a response.
Callback task creation
Ask what the customer wants to discuss and when they prefer to be contacted, then create a native CRM task linked back to the WhatsApp conversation.
Lead capture for visitors
Non-registered contacts can be restricted to a verified callback or enquiry route. Their name, number, email and reason are collected before one native lead is created for follow-up.
Team hand-off
When the assistant should stop, the enquiry can be passed to the team without inventing an unrelated record. The person taking over can see what has already been asked and answered.
Editable messages and confirmations
Administrators can control branch wording, prompts and confirmations. Customer and internal email confirmations can be sent for supported ticket, callback and hand-off outcomes.
See conversations as they arrive
A low-latency live channel keeps the permission-scoped inbox and header indicator current across accessible active accounts, with bounded recovery if the primary channel is interrupted.
Take over at any point
An authorised person can open the same conversation, review the context and reply directly. The customer stays in one chat instead of being asked to repeat the request in another channel.
Continue from your linked WhatsApp
Because the account remains a linked WhatsApp device, the conversation can also be visible through the normal WhatsApp experience on the authorised phone, subject to your operating policy.
Account and conversation affinity
Replies remain on the WhatsApp number that received the conversation. Additional linked numbers do not silently replace the sender or bypass the shared delivery controls.
Assignments and ownership
Use assignments, priorities, tags and internal attribution to make responsibility visible. Teams can search for a conversation and understand who acted without relying on a separate spreadsheet.
Real read acknowledgements
Unread states are reconciled against WhatsApp and actual read acknowledgements are used, helping the header badge and inbox avoid becoming an unreliable parallel count.
Shared operational inbox
Work with unread states, assignments, priorities, tags, search, attachments and acknowledgements from one workspace designed for more than one authorised staff member.
Match and convert CRM records
Match contacts by telephone where appropriate and convert conversations into tasks, support tickets or leads through the CRM’s native models rather than an isolated shadow database.
Customer and portal history
Conversation history can appear inside the authorised customer profile and the contact-owned client portal, making past communication easier to review alongside the wider relationship.
Attachments and audit history
Retain message history, supported media, staff actions, downloads, conversions, connection changes and failures in a permission-controlled audit trail.
Controlled self-service lookups
Where compatible providers are installed and enabled, verified customers can be offered ownership-scoped lookups for items such as invoices, estimates, projects, subscriptions, tickets and detected orders.
Durable delivery queue
OTP, automated and staff replies share a durable outbound queue with one aggregate rolling ceiling of 30 dispatched messages per minute and continuation as capacity becomes available.
Time-limited one-time codes
Verification codes are password-hashed, single-use, time limited and protected by attempt limits. Resend and change-email recovery paths can be offered without treating them as failed code attempts.
Registered customer checks
Use exact registered-email verification for an unrecognised number, conditionally update the contact number after successful verification and retain session-wise evidence for review.
Restricted visitor route
A non-registered visitor does not receive customer account data or ticket options. The contact can complete only the configured, email-verified callback or enquiry route.
Role-based administration
Account viewing, replying, CRM conversion, standard replies, audit access and management actions remain subject to staff permissions and account access rules.
Compliance-friendly evidence
Verification events, automated actions, staff activity, connection changes and conversions are recorded so administrators can investigate what happened without exposing unnecessary credentials.
Isolated persistent sessions
Each WhatsApp account has an isolated linked-device session and runtime state. A session remains available until it is explicitly unlinked or invalidated by WhatsApp.
When your team is busy
Keep the first response useful without pretending every enquiry is the same
Property communication is often repetitive at the beginning and highly specific later. The assistant handles the structured opening, then leaves room for a person to apply judgement when the issue becomes sensitive, commercial or unusual.
Answers first-contact questions
Give customers clear, approved routes for common property, service and account enquiries instead of leaving every new message in an unstructured queue.
Books or prepares appointments
Capture the service, property, preferred date and time, then move the request into the connected Appointments workflow or the team’s agreed booking route.
Arranges callbacks properly
Collect the reason, preferred date, time and timezone and create a linked task so the callback is owned, visible and less likely to be forgotten.
Hands the chat to your team
Let a staff member take over instantly, reply from the shared inbox or continue through the linked WhatsApp account with the previous context still available.
From first message to human service
A practical WhatsApp workflow that stays connected to Proplix
The exact branches are configured around your organisation, but the operating pattern remains clear: capture the message, understand the route, verify the person when necessary, create or connect the next action and bring in a person whenever the conversation needs them.
- 1CaptureReceive the WhatsApp message and attach it to the correct linked account.
- 2QualifyAsk focused questions, identify the likely route and collect useful context.
- 3VerifyRecognise the registered number or use email and OTP checks where required.
- 4Book or routeCreate the supported ticket, callback, lead or connected appointment journey.
- 5Human takeoverLet the right team member join, continue live and keep the full conversation history.
Designed around real property communication
Useful for letting, property management, compliance and service teams
A WhatsApp assistant is most valuable when it does more than send a generic greeting. Proplix can shape the first-contact route around the records and decisions your team already manages. A letting team may use it to capture an applicant’s preferred area, move-in date and viewing request. A property manager may use it to identify a tenant, understand a repair or arrange a supplier callback. A compliance team may use it to collect the property reference, certificate type and requested visit window before the enquiry reaches the responsible person.
The customer receives a faster and more organised response, while your staff receive better context. The conversation remains visible in the shared inbox, and supported outcomes can be reflected in the CRM as a lead, ticket, task or connected customer history rather than being left only on one person’s phone.
Official operating guidance
Continue with detailed Help Centre instructions
Open the maintained Britixo Help Centre in a new tab for administrator setup, permissions and workflow guidance. You can keep this product page open while reviewing the deeper technical and operational articles.
Powering responsive property teams
Ready to put WhatsApp to work for your team?
Discuss the customer journeys, appointments, callbacks, verification and takeover rules you want Proplix to support.
- Set up by Proplix specialists
- Works with linked WhatsApp
- Controlled, auditable and property-focused