Field data that reaches Salesforce, even with no signal.

Design a form, collect it on Android phones offline, and Salma writes each visit into your own Salesforce.

Talk to us How it works
The Salma Console's sync history: each submission with its form, its Salesforce status (failed, too large, synced with files pending, waiting) and what happened, with buttons to fix the mapping or resend.

The Salma Console, sync history. Sample data.

One trip for every visit, from the form to your CRM.

  1. Design the form

    Build it in the Console: questions, choices, rules and lists of people.

  2. Give it to your team

    Choose which officers get each form. Each phone sets up with one code.

  3. Collect offline

    Officers fill it in on an Android phone, with or without signal.

  4. Sync when there is signal

    Finished visits send themselves as soon as the phone finds a network.

  5. Check it in Salma

    Every submission arrives in the Console, with the form version it used.

  6. Send it on

    Salma writes it into Salesforce. Power BI is next.

Waiting is normal: offline is how fieldwork works.Sent means it is in your Salesforce.

Built for days without signal.

  • Lists on the phoneThe people an officer visits, thousands of them, are on the phone. They pick a name and the form opens for that person.
  • Finish once, it sends itselfA finished visit waits on the phone and goes as soon as there is signal. The phone says whether it was sent.
  • Low-cost Android phonesRuns on Android 8 or later.
Salma on a phone: Home with Forms, Saved for later and Waiting to send, and the line All sent.
Home
A form on the phone, opened for the person picked from the list, whose name shows under the form title.
A visit to one person

The Salma app on an Android phone. Test data.

Run the whole field team from one screen per officer.

An officer's screen in the Console: details, access on, the phones they are signed in on with Show setup code and Sign out all phones, and a preview of what their phone shows.

The Salma Console, one officer. Sample data.

Their forms and lists. Tick what each officer gets. Their phone gets it at the next refresh.

Access on or off. Turn an officer off and their phones stop sending. Turn them back on and nothing needs setting up again.

A lost phone. Sign out all of an officer's phones. Unsent visits stay on the phone, never deleted without a warning.

Straight into your own Salesforce.

Nothing installed in your org
Your Salesforce admin creates one app for the login and signs in once. Salma installs no package.
You choose where answers go
Map each question to a Salesforce field in the Console. One visit can create or update several records.
No duplicates
Each record carries a Salma Id, so sending a visit again updates the same record instead of making a copy.
You see what failed, and why
The sync history says in plain words what Salesforce refused. Fix the mapping and resend.
Field staff need no Salesforce licence
Officers only use the Salma app. Salma writes to Salesforce as one integration user.

Power BI is next. Other CRMs after that.

Questions

Does it work without internet?

Yes. Officers fill in forms with no signal. Visits stay on the phone and send when it finds a network.

Do we need Salesforce?

No. Every visit lands in the Salma Console, where your team can read it. Salesforce is where Salma sends it on, once you connect one.

What can a form do?

Text, numbers, dates, choices, photos, GPS location and a pick from a list of people. Questions can share one phone page, show only when an earlier answer calls for it, check the answer, and calculate values.

Which phones does it run on?

Android 8 or later, including the low-cost models most field teams carry.

Is our data kept apart from other organisations?

Yes. Each organisation's data is kept separate in the database itself, not only in the screens.

See it with your own forms.

Talk to us