Problems we solve

Another system the reps won't open

You've piloted field apps before. Separate logins, separate data and a sync to Salesforce that breaks, and six months later the reps are back on email.

What it looks like today

  • Reps juggle another username and an app that doesn't know their accounts.
  • Field data sits outside Salesforce and has to be integrated, reconciled and secured separately.
  • Every change to a form or a label is a vendor request.

What changes

FieldKo installs from AppExchange into your own Salesforce org. Reps log in with their Salesforce username and see their own accounts. Field data becomes Salesforce records under your permissions, and your admin configures menus, visit actions, surveys and labels from Salesforce settings.

Examples

See it fixed, one visit at a time.

On the phone

Monday morning download

A rep logs in with her Salesforce username and her whole week (accounts, visits and surveys) is on the phone before she leaves home.Offline syncStore visits & call cyclesMia · Field rep · North Shore territoryOn the phoneWorks Offline

Store history before walking in

Before walking into a pub, the rep sees the last visit's notes, score, open tasks and order, so the conversation starts where it left off.Store visits & call cyclesOffline syncBen · Field rep · The Royal Hotel, LeichhardtIn Salesforce

Installed from AppExchange in an afternoon

A Salesforce admin installs FieldKo from AppExchange, assigns permission sets, and reps log in with their existing Salesforce username.Salesforce setupChris · Salesforce admin · Head officeIn Salesforce

Rename it to what the business calls it

An admin renames menu items and visit actions to the company's own terms from Salesforce settings, with no code and no vendor request.Salesforce setupChris · Salesforce admin · Head office

Store names, people and figures in these examples are illustrative.

See it in your own org.

We'll install FieldKo in a sandbox and run a visit with one of your reps.

Book a Demo