# Salesforce mobile app for reps: what to log from the road, and the weekly check that it landed on the opportunity https://salesbond.app/blog/salesforce-mobile-app-rep-activity-manager-check/ Published: 2026-10-24 · Updated: 2026-10-24 Reps can view and update records, log calls and create tasks from the Salesforce mobile app, but an activity only helps the manager if it is attached to the right opportunity with an outcome and a next step. Check once a week for open opportunities whose latest activity was logged without a related record. This is not a download guide. It is about what a call logged from a parking lot turns into inside Salesforce, and how to tell when it turned into nothing a manager can use. ## The phone is where the CRM gets skipped At a desk the rep is already in Salesforce when the call ends, and the note takes thirty seconds. After a site visit the rep is in a car, then in the next lobby, then at dinner. The record gets written on Friday from memory, and by then “they are reviewing the proposal” has replaced “the ops lead wants the delivery clause changed before she signs”. We think honest pipeline data is won or lost in the ten minutes after a conversation, and for a field rep those ten minutes happen on a phone. The useful question is not whether the app is installed. It is what the minimum entry from the phone is, and whether it lands where you will look on Monday. ## What the Salesforce mobile app does from the road, and what it does not Yes Salesforce runs on a phone. The app is a download from the App Store or Google Play, it runs on iOS and Android, and reps log in and work with the same records they see in Lightning Experience on the desktop ( [Trailhead: Get Started with the Salesforce Mobile App](https://trailhead.salesforce.com/content/learn/modules/salesforce1_mobile_app/salesforce1_mobile_app_intro)). Trailhead’s own example is a sales rep editing an opportunity from their phone, so changing a field or two is ordinary mobile work. Logging a call and creating a task are too. One mechanic shapes everything below. Log a Call does not create a “call”. It saves a completed task (Type set to Call, Status set to Completed) that then shows on the record’s activity timeline ( [Supered: how to log a call in Salesforce](https://www.supered.io/blog/log-a-call-in-salesforce/)). If the rep’s profile lacks create access on tasks, the save fails, and reps often close the error assuming the call was saved. So a logged call is a receipt for something that already happened. It is not a next step; we wrote up why that distinction matters in [Salesforce tasks that carry the next step](https://salesbond.app/blog/salesforce-tasks-next-step-rule/). On offline: Trailhead lists offline capabilities among the app’s features, but our routine does not lean on them. The rule is “same day”, not “same minute”, and a same-day rule survives a dead zone. ## Log a call from your phone in two minutes, before the engine starts The order is what makes the related record come out right. 1. Open the opportunity first. Not the contact, not the account. A call logged from the opportunity’s page has that opportunity in its Related To field. Log it from the contact’s page and the call is tied to the person; the opportunity gets it only if the rep also picks it in Related To, which on a phone rarely happens. 2. Log the call with one line of outcome. “Positive, will circle back” is not an outcome. “Wants net-60; said no to the onboarding fee” is. 3. Create the task for the next step, with a date. If the entry did not happen the same day, treat it as reconstructed; a manager cannot tell those apart a week later. For teams that sell in person, what to write after a visit is in [field sales visit logging in the CRM](https://salesbond.app/blog/field-sales-visit-logging-crm/); the version here adds step one, because on a phone that’s where things go wrong. ## Calls and tasks that land on nothing A rep we will call Priya runs a strong week. Nine customer calls logged from her phone, each with a decent note. Her manager opens the Dunmore opportunity before their 1:1 and sees a timeline that ends three weeks ago. Both views are true. Priya logged the Dunmore calls from the contact’s page, because that is where the the phone number was. Salesforce shows an activity on the records it is related to (Trailhead’s [activities unit](https://trailhead.salesforce.com/content/learn/modules/sales_admin_maximize_productivity/sales_admin_maximize_productivity_unit_1) walks through a task that appears on both the account and the contact), and nothing put the Dunmore opportunity in Related To. So the calls sit on the contact. The opportunity, the record the forecast is built from, shows silence. Add two tasks she created from her task list with no related record at all and you have a rep whose activity count says busy and whose pipeline says abandoned. We treat an activity with no opportunity behind it as unlogged for pipeline purposes. The work was done, but nobody runs a pipeline review from the contact list, so a call recorded there is invisible exactly when it’s needed. ## The Monday check: opportunities nobody touched from the road ![Monday ten-minute check: three lists to pull from the activities report, each paired with the manager's action](https://salesbond.app/wp-content/uploads/2026/10/salesforce-mobile-app-rep-activity-manager-check-2.png) Ten minutes, no new fields. The lists come from an activities report: Salesforce’s activity reports show tasks, events and calls together with the contacts, accounts and opportunities they are related to (same Trailhead unit). Filter it to the last seven days and read three things off it: - Open opportunities with no activity in the last seven days. In the opportunities Kanban view a yellow triangle already flags a deal with no scheduled meetings or tasks; how to read the timeline behind it is in [reading the Salesforce Activity Timeline like a manager](https://salesbond.app/blog/salesforce-activity-timeline-deal-check/). - Activities from the week where the opportunity column is empty. - Reps whose logged calls all sit on contacts and none on opportunities. That one is a pattern, not an incident. What you do with them matters more. The first goes into the 1:1 as a question about the deal, not about the logging. The second gets a same-day request: relate these to the right opportunity, today. The third is a short refresher on step one, and after two weeks of asking it usually stops appearing. Run it on Monday morning and the week’s coaching is already decided. On Friday you are grading instead, which is a different and less useful conversation. ## Leave this for the desktop A few edits we ask reps not to thumb in between meetings: a stage change that triggers required fields, a new amount or close date, a merge or a delete, and a note longer than a paragraph. The phone can do them. Each of them changes what the forecast shows though, and a change made in a lobby in forty seconds is the one nobody can explain later. The phone is for what happened and what happens next. The desk is for what the deal is worth and where it stands. ## When the phone is the wrong place to fix data If the Monday check turns up twenty activities with no opportunity, the answer is not twenty edits from a phone on Tuesday afternoon. This week’s records need relating, a desk job with the report open. Next week’s records need the habit, which is a conversation. Fix the habit and the list shrinks on it’s own. Fix only the list and you will be fixing it every Monday. A disclosure, since we are on finding these without building the report yourself: we build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive, and today it works with Salesforce as well. Its Deal Health checks open opportunities against more than 20 rules, activity among them, and explains which deals need attention and why. It can only read what landed on the opportunity, so the two minutes in the parking lot still decide. [Check your CRM with SalesBond](https://salesbond.app/) after a week of same-day entries.