Answers for every stage of the journey.

L2S Proximity is a global sales-productivity platform combining CRM, sales pipelines, field operations, reporting, inventory, the Sophia AI companion and WhatsApp automation in one tenant-based workspace.

No. The platform is designed for organisations and sales teams worldwide. Phone numbers should be entered in international format, and organisations remain responsible for the laws that apply where they operate.

Select Start free trial, enter the account owner’s name, email, phone and password, then provide the company name, industry and contact details. In the final step, add the headquarters location information requested and submit the registration.

Prepare the account owner’s contact details, company name, industry, company phone and email, headquarters address and—if used—headquarters coordinates. Also decide who will administer the workspace and which people need agent, manager, director, accountant or administrator access.

The account owner signs in to the isolated company workspace, reviews the company settings, creates employee accounts, configures roles and starts WhatsApp onboarding for the people who will work with Sophia.

Yes, where the account has multiple active memberships. After sign-in, select the company workspace you intend to use. Always verify the selected company before entering or importing records.

A basic workspace can be opened quickly. The total time depends on the number of agents, data to import, permissions, WhatsApp verification and how much the business wants to customise its workflow.

An authorised manager or administrator opens Settings, then Users, selects Add employee, enters the agent’s full name and WhatsApp number in international format, chooses Sales agent, and selects Create account & verify. L2S generates a login ID and temporary password and queues WhatsApp verification.

The account workflow produces a login ID and one-time temporary password and begins the verified WhatsApp onboarding flow. The administrator should share credentials through an approved secure channel and never keep a reusable copy of the agent’s private password.

Sign in with the issued login ID and temporary password. The system requires the agent to replace that temporary password with a private password before entering the company workspace.

The administrator starts or restarts WhatsApp onboarding from Settings › Users. The agent completes the verification message sent to the registered WhatsApp number. Assistant access activates only after the number is verified.

The workspace supports sales agent, manager, director, accountant and administrator roles. Available pages and actions depend on the assigned role and the organisation’s configuration.

Managers can provision sales-agent accounts. Director or administrator access is required for higher-privilege roles, helping prevent accidental privilege escalation.

Open Settings › Users. Authorised administrators can change the role directly or open Manage account to update the person’s name, email, WhatsApp number and active status.

Use the guided Remove agent or deactivation workflow rather than sharing or recycling the account. Review the handover preview, transfer live work to an appropriate replacement, confirm the reason and remove access promptly.

Begin with assigned priorities and overdue follow-ups, capture every new lead, log meaningful contact, update status and notes, schedule the next action, then record the deal, sale or payment when the outcome occurs.

A lead is a person or organisation with potential interest that is still being qualified. A customer is an established relationship with a fuller history of interactions, documents, reminders and commercial activity.

Capture a reliable name and contact method, source, product or service interest, location preference where relevant, assigned owner, useful context and a dated next action. More complete records produce better follow-up and reporting.

End each meaningful conversation with a recorded outcome, current status, note and next step. Agents can make these updates from the dashboard, mobile workflow or through Sophia on WhatsApp where supported.

Supported interactions are recorded as activity against the relevant lead or customer. This creates a timeline and contributes to agent-activity reporting rather than leaving communication disconnected from the record.

Create a deal when the opportunity has enough commercial detail to track value, stage, probability, expected close date and ownership. Keep the linked lead or customer context current as the opportunity moves.

Use the Sales workflow in the dashboard or give Sophia a clear instruction containing the customer, amount, currency, date, payment state and responsible agent. Review the resulting confirmation and record after submission.

Yes. Industry-aware inventory workflows can hold property or vehicle records and connect customer interest, availability and sales activity to the wider operation.

Sophia is the L2S Proximity AI sales companion. She helps authorised agents and managers capture work, retrieve reports, identify follow-up gaps and coordinate agent accountability through a natural WhatsApp conversation.

No. Supported actions can be requested through Sophia or completed in the mobile experience. The dashboard remains the best place for broad review, complex corrections, administration and detailed verification.

State the action, identify the person or record, provide essential details and give the next step or timing. For example: ‘Record a lead for Alex Morgan, +44…, interested in Enterprise, assign to Priya and follow up Friday.’

Yes, when the action is enabled for the authorised user. Include names, phone numbers, amounts, currencies, dates and ownership clearly, then check Sophia’s confirmation.

Yes. Ask for a period, team and measures such as leads, sales value, conversion, overdue follow-ups, calls, SMS, check-ins or top agents. The answer depends on records available to the requesting user.

Authorised managers can ask Sophia to identify agents who need attention and initiate supported accountability or status follow-ups. Responses and resulting actions are designed to remain reviewable.

Reply in the same conversation with the missing detail. Do not guess high-impact facts. If several similar records exist, use a full name, phone number, company, record reference or another distinguishing detail.

Give a precise correction and review the confirmation. For material amounts, identity changes or uncertain matches, open the dashboard and verify the final record and activity history.

No. Never share passwords, one-time codes, payment-card data or unnecessary sensitive personal information in a Sophia conversation.

It supports field check-ins, quick customer and sales updates, mobile activity capture and a more accurate view of agent execution while work is happening away from a desk.

With device permission, the app can record the GPS point associated with an explicit sign-in or work check-in. The time and location can then be shown to authorised company management.

Where route tracking is enabled for the organisation and the agent grants the required device permission, the mobile workflow is intended to calculate distance travelled during an authorised work session. A check-in-only configuration records the submitted point rather than continuous live movement.

Where supported by the mobile operating system, rollout and granted permissions, the app can record business call activity such as the number called, time and count so reports reflect work accurately. It does not imply call-audio recording.

Where supported and permitted, the app can record SMS activity metadata, including the destination phone number, time and count. Organisations should configure this only for legitimate business use and provide required notices.

Supported call and SMS activity contributes to agent-performance and period reports, helping managers compare activity with leads, follow-ups, sales and outcomes.

It should not be. Device permission prompts and organisational notices explain the enabled tracking. Organisations are responsible for obtaining any consent or other lawful basis required in each country where they operate.

The related mobile reporting may be incomplete or unavailable. Core authorised CRM workflows can still be used where they do not depend on that permission. Check device settings or contact the company administrator.

Depending on role and available data, reports can cover pipeline value, lead sources, conversions, sales, payments, agent activity, calls, SMS, field check-ins and follow-up performance across a chosen period.

Check the selected date range, company workspace and agent filter. Confirm agents recorded activity against the correct lead or customer and that required mobile permissions or integrations were active at the time.

Yes. Compare activity with outcomes, look for overdue priority leads, inactive deals and inconsistent follow-up, then discuss the context with the agent instead of judging performance from one number alone.

Supported changes are reflected as the underlying records update, although network, processing and integration delays can affect exactly when an event becomes visible.

Authorised users can ask Sophia for a scoped summary such as today’s sales, overdue follow-ups or agents requiring support. The response follows the requester’s access and available system records.

Sign in, open My profile, edit Personal details and select Save profile. Your email is also your login ID. Enter the current password when changing the email or phone number; changing only the name does not require it.

The old WhatsApp assistant binding is disabled. An administrator must verify the replacement number and restart WhatsApp onboarding before Sophia access becomes active on it.

Open My profile, enter the current password, choose a new password of at least eight characters, confirm it and select Change password. Other signed-in sessions are revoked after a successful change.

An authorised administrator can open Settings › Users, choose Manage account and generate a temporary password. It is shown once; the agent uses it to sign in and creates a private replacement.

Use a unique password, keep credentials private, sign out of shared devices, reject unexpected requests for codes, keep software updated and report suspicious access immediately.

Each organisation operates in a tenant workspace. Membership and tenant-aware access checks are used to keep company records within the appropriate organisation context.

Visit the Security page and open each control for details about encrypted connections, role-based permissions, tenant isolation, protected sessions and auditable operations.

Confirm the login ID and password, remove accidental spaces, check Caps Lock, confirm you are online and retry in a current browser. New employees must use the issued temporary password and then create a private password.

Temporary passwords are intended for initial or reset use and may be replaced after successful use. Ask an administrator to confirm the login ID and generate a new temporary password if necessary.

Your membership may be inactive, still provisioning or associated with another login. Ask the company administrator to check Settings › Users and confirm your account is active in the correct tenant.

Access is role-based. Your role may not permit that page or action. Ask an administrator to verify your responsibilities rather than sharing another person’s account.

Confirm you are messaging from the verified number, your company membership is active and WhatsApp onboarding shows verified. Check connectivity, wait briefly for processing, then ask an administrator to restart onboarding if needed.

Confirm the action produced a success message, refresh the record, check the selected company and filters, and search using a unique phone number or record reference. Avoid submitting the same sale or payment repeatedly while the first result is uncertain.

Enable device location services, allow location for the app or browser, move to an area with a clearer GPS signal and retry. If it times out, check connectivity and battery-saving restrictions.

Confirm the organisation enabled the feature, the operating system supports it, the required permissions were granted and the activity occurred during the relevant reporting period. Some device or app-store policies can limit available metadata.

Reload the page, close and reopen the tab, confirm you are on l2s-proximity.co.ke and try a supported browser. If the issue remains, note the page, time and visible error before contacting support.

Send the affected page, approximate time, company name, what you expected and what happened to info@l2s-proximity.co.ke. Include a screenshot only after removing unnecessary personal data; never send passwords or one-time codes.