Working Deals From Your Phone: What a Mobile CRM Needs

Brokers do not stop working when they leave the desk. The question is whether the calls, texts and decisions they make on the move end up on the deal or in their pocket.

A merchant calls back while you are in line at the pharmacy. They have the statement you asked for and a question about the offer. You answer on your personal phone, talk for six minutes, promise to send something over tonight, and then try to remember the details at nine o'clock when you open your laptop.

Every funding broker has done some version of this. Work happens away from the desk, at a kid's game, between appointments, on a train. The trouble is not the location. It is that a mobile conversation on a personal device often leaves no trace on the deal, so the manager cannot see it, the next broker cannot pick it up, and your own memory becomes the system of record.

A mobile CRM is supposed to fix that. Plenty of products technically run on a phone, though, and still fail the moment you try to work a real deal on one. Here is what actually needs to be there.

Pre-flight summary

  • Judge a mobile CRM by timing real tasks, not by reading a feature list.
  • Calls and texts must come from company numbers and log to the deal automatically.
  • Phones need compact deal context; iPads suit statement and offer reviews.
  • Mobile access must follow the same roles and audit trail as the desktop.
  • Two-factor sign-in and keeping documents in the CRM protect lost devices.

Leg 01The test: can you finish a real task in under two minutes?

The simplest way to judge a mobile CRM is to stop thinking about feature lists and try real tasks. Stand up, take your phone and time yourself. Call a merchant back from the deal record. Send a follow-up text. Find out which documents are still missing. Check whether an offer came back from a lender.

If any of those takes more than a couple of minutes, or forces you to switch to your personal phone app or messages, brokers will quietly route around it. Whatever they route around stops getting logged.

Leg 02Calls and texts that land on the deal

Calling is the core of the job, so it is the first thing that has to work. A broker on the move should be able to call or text a merchant from inside the CRM using the company's numbers, with the call and message logged to the deal automatically.

That does three things. It keeps the merchant seeing your company's number rather than a broker's personal one. It gives the manager visibility into activity that would otherwise be invisible. And it means that when the broker is out sick next week, a colleague can open the deal and see that the merchant called back on Tuesday evening with a question about the payment schedule.

FundPilot runs on desktop, iPad and iPhone, and its built-in dialer covers browser calling and two-way texting, with every call logged to the deal, so the same record follows the broker from desk to phone.

If a call is not on the deal, as far as the rest of the floor is concerned, it never happened.

Leg 03Enough deal context to have a real conversation

When a merchant calls you unexpectedly, you need about thirty seconds of context before you say anything useful. Who is this, what stage is their deal in, what did we last talk about, what are we waiting on?

On a phone screen, that context has to be compact. The latest notes, a short summary of the last recorded call, outstanding documents and current stage should be visible without scrolling through a desktop layout shrunk to fit. Searchable call transcripts with summaries help a great deal here, because you can glance at what was said rather than relying on whatever notes were typed.

  • Current stage and next action
  • Last call summary and recent texts
  • Documents received and still missing
  • Offers received and their status
  • Who else on the team has touched the deal

Leg 04Where the iPad fits

Phones are for quick actions. An iPad is better for the work that needs a bigger screen but not a desk: reviewing a statement with a merchant across a table, walking through an offer comparison, or reading a lender's reply in full.

Say you are meeting a contractor at their yard. On an iPad you can open the deal, review the deposits and balances from their statements with each figure linked to its page, and show them side by side how two offers compare on cost and payment schedule. That is a much better conversation than reading numbers off a phone.

Leg 05Approvals and decisions on the move

Managers and owners often need to act away from the office too. A broker wants a manager to look at a file before it goes to a lender. A payout needs checking. A question comes in from an investor about a participation.

Mobile access helps only if it respects the same permissions as the desktop. A manager should see and act on what their role allows, a broker should see their own deals, and every action should land in the audit trail the same way it would from a desk.

Say a broker texts their manager from a merchant's office asking whether a file with a recent NSF is worth submitting. The manager should be able to open the deal on their phone, look at the statement figures and the broker's notes, and reply with a decision that is recorded on the deal, rather than in a private text thread that nobody else will ever find.

Leg 06Security for devices that leave the building

Phones get lost. Tablets get left in cars. A mobile CRM holding merchant financial data needs basic protections that do not depend on the broker remembering to be careful.

  1. Require two-factor sign-in for every user, including on mobile.
  2. Keep merchant documents inside the CRM rather than downloading them to the device.
  3. Use role-based access so a lost device exposes only what that user could see.
  4. Review the audit trail for unusual downloads or exports.
  5. Have a clear process for disabling access when a device is lost or a broker leaves.

Questions from the floor

Should brokers ever use their personal phone number with merchants?

It is better to avoid it. Calls from personal numbers are not logged on the deal, the merchant ends up attached to an individual rather than your company, and you lose visibility if that broker leaves. Calling and texting from inside the CRM using company numbers keeps the record complete and the relationship with the business.

Is it safe to review bank statements on a phone?

It can be, provided the documents stay inside the CRM rather than being downloaded or forwarded, the account uses two-factor sign-in, and access is limited by role. The bigger risk is usually habits, such as screenshots or saving files locally, so set a clear policy and review your obligations with qualified counsel.

Do brokers need a separate dialer app on their phone?

Not if the CRM's dialer works on the device. FundPilot's dialer supports browser calling and two-way texting from the deal record, and the platform runs on desktop, iPad and iPhone, so calls made on the move are logged in the same place as calls made at a desk.

General information only — not legal, tax or financial advice. Rules for telemarketing, texting, recording, disclosures and data retention vary and change; confirm current requirements with qualified counsel.

See your version

Put this playbook
inside your own CRM.

Book a walkthrough →