What makes Strkr's app different from Salesforce Mobile?
Three structural differences. First, mobile-first design: Strkr's mobile surfaces are designed for phone-screen moments (pre-call briefing card, voice-note capture, quick-draft follow-up), not scaled-down desktop views. Salesforce Mobile presents a shrunken desktop UI that reps find friction-heavy. Second, consolidated primitives: Strkr's mobile app includes CRM, enablement content, playbook, risk flags, and expense capture in one surface. Salesforce Mobile covers CRM only; reps running the Salesforce + Highspot + Concur stack have to switch three apps. Third, voice-note capture with AI structuring: Strkr's voice-to-structured-log workflow replaces desktop typing with 2-minute post-meeting dictation. Salesforce Mobile supports voice-to-text in notes fields but does not auto-structure into activity log, methodology-primitive updates, and next-step tracking. The practical outcome: field reps report using Strkr's mobile app during the selling day in ways they never used Salesforce Mobile.
How does the voice-note capture handle accented speech and technical terminology?
The voice transcription engine supports multiple English dialects (US, UK, Australian, Indian), Spanish, French, German, and additional languages with varying accuracy per language. Heavy accents in English generally transcribe at 85-92 percent accuracy; standard American and British English transcribe at 95-98 percent accuracy. Technical terminology (medical device names, legal clauses, specialized industry jargon) is handled through a custom vocabulary surface: admins can upload specialized terms (product names, acronyms, industry-specific vocabulary) to improve recognition on known terms. Reps running in environments with heavy accents or specialized vocabulary should expect to spot-check transcribed notes before relying on them. The structuring step (parsing the transcription into activity log, next step, methodology-primitive updates) runs on top of the transcription, so a transcription with 92 percent word accuracy typically produces an 88-93 percent accurate structured output. For critical note-taking (regulated environments, legal matters), reps should use voice-note as a draft and refine from the desktop.
How does the offline cache work?
The offline cache stores three categories of content on the device. First, recently-used content (default: last 20 pieces opened within the last 30 days). Second, favorited content (rep marks specific one-pagers, case studies, ROI calculators as favorites, up to 50 items). Third, account-tied content (content attached to specific deals in the rep's active pipeline). The total cache size is configurable per device, with defaults around 500MB on phone and 2GB on tablet. The rep can see cache status in app settings and manually trigger a cache refresh before entering a low-connectivity environment. Edits made offline (voice notes, activity logs, draft emails) queue locally and sync automatically on reconnect. Conflict detection runs on sync: if the same record was edited on another device while offline, Strkr surfaces the conflict with both versions for manual resolution. The practical pattern: field reps in regular low-connectivity environments pre-cache before trips; reps in standard connectivity environments rely on the automatic recently-used caching.
What integrations does the mobile app support for expense capture?
Native integrations ship for Concur, Expensify, Ramp, Brex, and Divvy. The photo-of-receipt workflow captures the receipt image, extracts expense data (merchant, amount, date, category) via OCR, and submits to the expense tool with the deal association included as metadata. The expense tool handles the approval workflow and payment; Strkr maintains the deal-to-expense link for ROI math. Teams running expense tools without a direct Strkr integration can use the generic CSV export of expenses to attach to deals manually. The practical workflow: rep snaps the receipt in the Strkr app, taps the deal to associate, and the expense submits to Concur or Expensify with the deal metadata attached. Finance sees the categorized expense in their tool; sales ops sees the deal-tied expense in Strkr for ROI math. The integration eliminates the manual deal-tagging step that reps typically skip.
Does the app work on tablets and in-vehicle screens?
Yes. The app ships for iOS (iPhone and iPad), Android (phone and tablet), and web (desktop and in-browser mobile). The iPad experience is optimized for field reps running demos on tablets: landscape orientation, split-screen with content on one side and account context on the other, Apple Pencil support for in-meeting note-taking that transcribes to the activity log. Android tablet support is comparable. In-vehicle screens (CarPlay, Android Auto) are supported for voice-note capture only: reps can dictate activity notes while driving between meetings without touching the phone. The in-vehicle experience is intentionally limited (no content browsing, no detailed data display) to maintain driving safety. Smartwatches (Apple Watch, Wear OS) are supported for push notifications and a quick-glance pipeline summary; the primary workflow runs on the phone or tablet. The multi-device coverage lets field reps use the right device for the right moment: phone for quick lookups between meetings, tablet for in-meeting demos, in-vehicle for driving dictation, desktop for admin and deep analysis.
What are the limits of a mobile sales enablement app?
Three real limits. First, the app is not a substitute for desktop. Deep pipeline analysis, admin configuration, methodology rollout planning, and reporting deep-dives still need a desktop surface. The app complements the desktop; it does not replace it for admin and analytical workloads. Second, voice transcription has quality limits. Heavy accents, noisy environments, and highly specialized vocabulary degrade accuracy. Reps in those contexts should spot-check transcribed notes. Third, the app is leverage on good reps, not a substitute for selling skill. The pre-call briefing and post-meeting voice-note capture compress the daily workflow, but the actual client interaction still requires rep capability. Teams expecting the mobile surface to generate pipeline without rep skill investment see partial returns. Teams that understand these limits and give field reps the right device for the right moment typically see substantial field-productivity gains; teams expecting the app to fully substitute for desktop or compensate for weak reps see partial coverage.
