Skip to main content
GPTfy - Salesforce Native AI Platform

One Sentence. Two Records.

Tell your GPTfy agent you met someone new. It creates the contact, logs the visit, and links both to the right account; no forms, no navigation.

Reps skip CRM updates because logging one new contact means finding the account, creating the contact, filling out an activity form, and linking it all together. This demo shows a rep doing all of it from one plain-English request, inside the Salesforce app they already carry.

Capabilities shown

One Request, Two Records

  • Creating a contact and logging an activity are normally two separate jobs in Salesforce; one sentence does both.
  • Both records are associated with the right account automatically, with no lookup or navigation by the rep.

Asks Only What It Needs

  • The GPTfy agent detects that the person does not exist in Salesforce yet and requests the missing required fields.
  • In the demo it asks for two things only: last name and title. Everything else it infers from the request.

Structured Activity, Not Just a Note

  • The logged visit carries a written description of what was discussed, not a raw dictation dump.
  • Key points and conversation sentiment are captured on the activity record alongside the summary.

Skills: One Job Each

  • A skill is one specific job the GPTfy agent can do in the CRM; creating a contact and logging a visit is a single skill among several.
  • The rep asks in plain English and the agent selects the right skill, so there is nothing to learn or configure per request.

Use this video when

A field rep who just met a new stakeholder on site logs the person and the visit before leaving the parking lot

An account executive captures a new contact met at a conference without opening a laptop

A rep working an existing account adds a newly introduced decision-maker without hunting for the account record

A sales manager gets a real record of every relationship instead of the handful reps remembered to type up

A team handing an account to a new owner inherits complete contact and activity history rather than gaps

A mobile-first sales org keeps CRM data current in the field, where the conversations actually happen

Frequently asked questions

Yes. That is the scenario shown in this demo. The rep says they met a new person at a customer, and the GPTfy agent recognizes the person is not in Salesforce. It creates the contact under the correct account and logs the visit as a completed activity, treating what would normally be two separate jobs as one request.

Only what the GPTfy agent cannot infer. In the demo the rep says the person's first name, their company, and what was discussed. The agent then asks for two missing details required to create the contact: last name and title. It does not walk the rep through a form or ask for anything it already has.

A written summary of the conversation, the key points discussed, and the sentiment of the interaction. In the demo the activity reads that the rep met with Dave Miller at Rolling Hills Cattle Company and discussed the renewal process, with key points and sentiment captured alongside it.

A skill is one specific job the GPTfy agent knows how to do inside your CRM. Creating a contact and logging a visit is one skill. The agent in this demo also has skills for pulling up accounts, checking open deals, checking open cases, seeing what has happened recently, looking up a contract, and setting a follow-up. The rep asks in plain English and the agent picks the right skill.

No. GPTfy runs inside the Salesforce app reps already carry, so there is no new application to roll out, no second login, and no separate tool for reps to remember. That matters for adoption, because the CRM updates happen where the rep already is.

Dictation produces text that still has to be filed against the right records. Here the GPTfy agent acts on the request: it creates the contact, logs the activity, links both to the correct account, and structures the summary into key points and sentiment. The rep never navigates to a record or fills out a form.

Ready to see this in your Salesforce org?

Book a 45-minute session and we'll walk through this use case using your own data.

Video transcript
Every sales team has the same quiet problem. Reps finish a great meeting, and then the CRM work begins: find the account, create the contact, fill out the activity form, link it all together. It is tedious, and it is easy to skip. When it gets skipped, your customer history goes stale. So we built something different. It is not another app to install. It is right inside the Salesforce your reps already carry. Instead of forms and clicks, they just talk to their CRM in plain English. Let me show you the everyday version of this: a rep who has just met someone brand new, someone who is not in the system yet. In one sentence, I will tell the assistant that I met a new person at a customer. Normally that is two separate jobs, create the contact and then log the activity. Watch it do both, asking only for the one or two details it actually needs. Here is the request: I met Dave at Rolling Hills Cattle Company, and we talked about the renewal. The agent comes back asking for what it is missing. It needs Dave's last name and title to add him as a contact. Dave's last name is Miller, and he is a ranch manager. Creating a contact and logging a visit is just one of the skills set up in the agent. Think of each skill as one specific job it knows how to do inside your CRM. Today it also has skills for pulling up accounts, checking open deals, checking open cases, seeing what has happened recently, looking up a contract, and setting a follow-up. You ask in plain English, and the agent picks the right skill and does the work. So let's check the contact. The contact was created under the right account, Rolling Hills Cattle Company, and the title is Ranch Manager. Now the activity. Opening the details, I can see the comments: met with Dave Miller at Rolling Hills Cattle Company and discussed the renewal process. It is also showing me the key points and the sentiment. Here is what just happened. In a couple of sentences of plain English, with no forms and no navigation, a brand new contact was created and a completed activity was logged, both linked to the right account. The assistant knew the person did not exist, asked only what was required, and did the rest. Now multiply that across every rep, every meeting, every day. That is the difference between the CRM you hope your team is keeping and the one they will actually keep using, because it finally takes seconds instead of minutes. Cleaner data, better handoffs, and a real record of every relationship. This is CRM that works the way people actually want. You just talk, and it gets done.

Last updated: