Connect Salesforce

Updated Nov 20, 202620 min read
English
On this page

Connect your Salesforce org, and your team sees each customer's Contact or Lead next to the conversation, with a Contact's Account, open Opportunities and open Cases. Deskwoot links the people who write to you to their Contacts and Leads, logs each resolved conversation on them as one completed Task, and can add the people Salesforce does not have yet as Leads.

Each Deskwoot workspace connects one Salesforce org. Several workspaces of one company, for example one per brand, can connect the same org, each with its own access. Every Deskwoot plan can connect Salesforce.

Who can connect

  • In Deskwoot, an administrator connects Salesforce, because Deskwoot then writes to Salesforce by itself. A teammate with the permission Manage integrations can reconnect an existing connection or disconnect it.
  • In Salesforce, an admin installs the Deskwoot package and sets up the Salesforce user Deskwoot acts as. You sign in as that user when you connect.

Salesforce editions

Deskwoot reads and writes through Salesforce's API, so your edition needs API access. Enterprise, Unlimited, Performance, Agentforce 1 and Developer Edition have it. Professional Edition and Pro Suite need Salesforce's Web Services API add on, which Salesforce sells separately. Starter Suite has no API access. Without API access, connecting ends with This Salesforce org or user has no API access.

The Salesforce user Deskwoot acts as

Deskwoot reads and writes with the rights of the Salesforce user you sign in as. Every Deskwoot teammate sees what this user sees.

  • Create a user only for Deskwoot. It needs a full Salesforce license and MFA set up. An API only user or a Salesforce Integration user cannot sign in this way.
  • Do not use a user with View All Data or Modify All Data. The connection card then warns that every teammate reads all data of your org.
  • One Salesforce user can hold at most 5 Deskwoot connections: a 6th ends the one used least recently. Reconnecting takes no extra place. Use another user from the 6th workspace on.

The permission set Deskwoot connection

The Deskwoot package holds only Deskwoot's sign in app. It brings no permissions, because a permission set from a package grants nothing in your org. In Salesforce Setup, your admin creates a permission set named Deskwoot connection and assigns it to the user Deskwoot acts as:

  • System permissions: API Enabled and Edit Tasks.
  • Objects: Read on Contacts, Leads, Accounts, Opportunities and Cases; Create on Contacts and Leads.
  • Fields Deskwoot reads: Contact Title, Email, Phone, MobilePhone and AccountId; Lead Title, Email, Phone and LeadSource; Account Type; Opportunity Amount and AccountId; Case Subject and ContactId.
  • Fields Deskwoot fills (Edit): Lead Email, Phone, LeadSource, Description and every field you give a value for new Leads; Contact Email, Phone, AccountId and Description; Task WhoId, WhatId, Description and ActivityDate.
  • If your org shares records privately: View All Records on Accounts, Contacts, Leads, Opportunities and Cases, or sharing rules that give the user those records.
  • For New customers to add Leads by itself, in any sharing model: View All Records on Contacts and Leads, and the system permission View Setup and Configuration, so Deskwoot can confirm that the user sees every Contact and Lead. Salesforce needs View Roles and Role Hierarchy in the same set for it.

Names, required fields such as a Lead's Company, owners and system fields such as a Case's number have no field permission in Salesforce, so there is nothing to tick for them.

The Deskwoot app's policies in Salesforce

  • Admin approved users: if your org lets only approved users use the Deskwoot app (Permitted Users: Admin approved users are pre-authorized), your admin also selects the Deskwoot connection permission set in the Deskwoot app's policies (External Client App Manager, Policies, Select Permission Sets). It must be your own set: Salesforce does not let a set from a package approve users.
  • Login IP ranges: if your org limits the IP addresses its users sign in from, set IP Relaxation to Relax IP restrictions in the same policies. Never add Deskwoot to your org's trusted IP ranges.

Connect Salesforce

  1. Go to Settings > Integrations and click the Salesforce card under CRM and real estate.
  2. Click Install the Deskwoot package and install it in Salesforce as an admin. Where Salesforce offers the choice, choose Install for Admins Only. Some editions, such as Professional Edition, offer only Install for All Users. That is fine: what Deskwoot may do comes from the permission set, not from the install.
  3. In Salesforce Setup, create the permission set Deskwoot connection and assign it to the user Deskwoot acts as.
  4. Back in Deskwoot, click Connect Salesforce and sign in as that user. If your org does not let you sign in on that page, choose Use Custom Domain there and enter your My Domain.
  5. Allow Deskwoot.

Salesforce then sends you back to the Salesforce page in Deskwoot, which shows Connected. There is nothing to import: Deskwoot reads Salesforce live and starts with the people who write to you after you connect. If Salesforce shows an error page or you cancel there, come back to the Salesforce page in Deskwoot and connect again. Deskwoot never sees your Salesforce password.

What Deskwoot reads and writes

Deskwoot asks Salesforce for API access and reads Contacts, Leads, Accounts, Opportunities and Cases when someone opens a customer or a send needs it. Every 5 minutes it looks up the people who wrote to you by their email address. Once a day it checks the user's rights and your org's API use and renews its access. It writes:

  • Tasks: one completed Task per resolved conversation, and the notes and tasks your team adds.
  • Leads: the people Salesforce does not have yet, only when Add new customers to Salesforce as Leads is on or your team clicks Create Lead.
  • Contacts: when your team uses Create a Salesforce contact.

Deskwoot keeps no copy of your Salesforce records. It stores which Contact or Lead belongs to which of your contacts, the Salesforce IDs of what it wrote there for 90 days, the org's name, ID and My Domain address, and the name, Salesforce username and ID of the user it acts as.

The Salesforce section in a conversation

In a conversation, the Details tab has a Salesforce section. The contact page has the same section under Connected systems, with everything Deskwoot sent for the contact. It shows the linked person's name with Open in Salesforce and:

  • for a Contact: Type, Owner, Title, Account, Account type and Account owner (only when it is not the Contact's owner);
  • up to 3 open Opportunities the Contact has a contact role on or of its Account, the one to close first on top, with stage, amount and close date;
  • up to 3 open Cases of the Contact that Deskwoot's user can see, the newest first, with a link to all of the Contact's Cases in Salesforce;
  • for a Lead: Type, Lead status, Owner (a user or a queue), Title and Company.

Stages and statuses show Salesforce's labels in the language of the user Deskwoot acts as. Amounts show no currency, because an org can hold several. A group the user may not read says Deskwoot's Salesforce user may not read them. Your team sees the section only for contacts whose conversations they can open.

When no person is linked, Deskwoot suggests the Contact or Lead with the same email address, else the same phone number. Your team can Link it, choose Not this person, or use Find person to search Salesforce Contacts and Leads by name, email or phone. Linking or unlinking changes nothing in Salesforce. Without a link your team can also add the customer:

  • Create Lead: a new Lead from the customer's name, company, email and phone. Salesforce needs a last name and a company. If Salesforce already has a person with that email address or phone number, the dialog offers to link it instead.
  • Create a Salesforce contact: Deskwoot links the Contact or Lead Salesforce has under the customer's email address, else adds a Contact under the one Account whose name is exactly the company in the form. The active Salesforce user with your teammate's email address owns it, else the user Deskwoot acts as.

Both need the permission Create clients, patients and contacts in connected systems. With a person linked, your team adds to Salesforce from the section:

  • Add a note: a completed Task named Note from Deskwoot, with the text, a link to the conversation and a reference.
  • Add a task: an open Task due when your teammate says, owned by the active Salesforce user with your teammate's email address, else by the user Deskwoot acts as.

When the link to a Contact is proven (a teammate linked the person, kept the link or added them, the customer verified their email address, or the customer wrote to you from an email address the Salesforce person holds), notes and tasks are also related to the Contact's Account.

New customers

Every 5 minutes, Deskwoot looks up the people who wrote to you in Salesforce by their email address and links the Contact or Lead it finds, a Contact before a Lead. The New customers card on the Salesforce page decides what else happens:

  • Add new customers to Salesforce as Leads, off by default: people Salesforce does not have yet become Leads, at most 200 a day. It turns on only while Deskwoot can confirm that its user sees every Contact and Lead (see the permission set), so it never adds a person Salesforce already has. After you change the permission set, click Sync now on the Salesforce connection.
  • Inboxes to look up in Salesforce: without a choice, every inbox except email inboxes, also inboxes you add later. Email inboxes are left out because they also get newsletters and vendor mail.

Deskwoot takes only people with an email address who wrote in the conversation themselves. It leaves out blocked contacts, spam, group chats, Discord conversations and Microsoft Teams channel threads. When a linked Contact or Lead is deleted in Salesforce, Deskwoot never adds that person again by itself while Salesforce stays connected; your team can still add them with Create Lead. When the 200 a day are reached, the connection card says so, and the people who write meanwhile are added only if they write again later. If Deskwoot can no longer confirm that its user sees every Contact and Lead, adding pauses and starts again by itself once it can.

Turning a switch on and choosing more inboxes need an administrator. A teammate who manages integrations can turn things off, choose fewer inboxes and change the New Leads card.

New Leads

The New Leads card decides how every Lead from Deskwoot goes into Salesforce, the ones New customers adds and the ones your team creates with Create Lead:

  • Lead Source: every new Lead gets it, so you find these Leads in your reports. When you connect, Deskwoot picks a source such as Web or Chat if your org has one.
  • Let your Lead assignment rules choose the owner: when it is off, a Lead New customers adds belongs to the teammate the conversation is assigned to, if an active Salesforce user has that teammate's email address, and every other Lead belongs to the user Deskwoot acts as. When it is on, your org's active Lead assignment rules choose the owner.
  • Values for new Leads: a value for each field your org requires on a new Lead. Salesforce refuses a new Lead without it.

A Lead New customers adds gets the person's name, email address, phone number and company, and a link to the conversation and a reference in its Description. When Deskwoot knows no last name or company, it fills in [not provided], as Salesforce's own web forms do.

Matched by email, not verified

A person Deskwoot found in Salesforce by email address shows Matched by an email given in chat, not verified until a teammate clicks Keep link, or picks the right person with Change person. Until then the conversation log goes only to the person, never to the Contact's Account or Opportunity, and Copilot is told to share no Salesforce details with the customer. Copilot treats a Lead that New customers added the same way. If the match is wrong, click Change person and choose the right Contact or Lead.

One Task per conversation

The Conversation log card decides which conversations go to Salesforce. With Log conversations in Salesforce on (the default) and in the chosen Inboxes to log (without a choice, every inbox), a resolved conversation in which the customer wrote goes to the linked Contact or Lead as one completed Task, dated the day it was resolved. When the conversation is resolved again after new messages, Deskwoot updates that same Task instead of adding another. It adds a new Task when the Task was deleted in Salesforce, another Salesforce user took it over, or the conversation is resolved again more than 90 days after it was last logged.

The Task is named after the conversation's number and inbox and written in your workspace's language and time zone. It says whether the customer was verified, holds the messages the customer saw (never internal notes) with card numbers that pass the Luhn check, valid IBANs and US Social Security numbers written as 123-45-6789 taken out (other numbers, such as ID card numbers, stay in), names who the conversation is assigned to in Deskwoot, and ends with a link to the conversation that only your team can open. Under a proven link, the Task of a Contact is also related to its open Opportunity when the Contact has a contact role on exactly 1 open Opportunity, else to its Account.

  • Every Task Deskwoot writes, and every Lead or Contact it adds through New customers or Create a Salesforce contact, carries one reference that starts with Ref dw-. Search Salesforce for it to find Deskwoot's entries, for example to answer a person's request about their data.
  • When a person is linked only after the conversation was resolved, Deskwoot logs conversations resolved in the last 7 days.
  • Deskwoot logs no group chats, Discord conversations or Microsoft Teams channel threads, no conversation in which the customer never wrote (such as a campaign nobody answered), and no ticket into which a merge brought another contact's messages.
  • Deskwoot writes the conversation logs and the Leads New customers adds at most 2 a minute to one connection. After you resolve hundreds of conversations at once, the Tasks arrive over a few hours.

API budget

Salesforce gives your org a number of API calls per 24 hours, shared by every app connected to it. On the API budget card you choose how much of it Deskwoot may use: 5, 10, 25 (the default), 50 or 100% of your org's calls. The card shows how many calls your org has used. What Deskwoot reads and does in the background stays within that share. What it writes goes out until Salesforce says your org's calls are used up. Background work also pauses once your org has used 90% of its calls, and the Salesforce section in conversations at 97%. A higher share needs an administrator.

AI and privacy

  • When a teammate uses Copilot in a customer's conversation, Copilot reads the linked Contact or Lead: its name, owner and title, a Lead's status and company, and a Contact's Account, open Opportunities and open Cases, as far as Deskwoot's user may see them. It never reads an email address, a phone number or a Case number, and nothing for a person that merely matches.
  • Deskwoot's server reads this data with fixed queries. The AI never calls Salesforce itself. The data reaches Deskwoot's AI provider Anthropic only to write the answer, and no Salesforce data trains an AI model.
  • Fynn, the AI agent that answers your customers, does not read Salesforce data. AI agents you connect to your workspace do not reach Salesforce through Deskwoot.
  • Deskwoot stores the Salesforce access encrypted in its database in the EU.
  • When a person's data is erased in Deskwoot, the link to their Contact or Lead and the records of what was sent for them are deleted too. You delete the person in Salesforce yourself.

Disconnect

Disconnect Salesforce at the end of the Salesforce page ends the connection. Deskwoot deletes its access, the links between your contacts and Salesforce records, and the Salesforce IDs it kept of what it wrote there. Deskwoot also ends its access in Salesforce. Copilot stops using Salesforce, and everything already in Salesforce stays there. If Salesforce does not confirm that the access ended, Deskwoot says so: revoke it in Salesforce under Setup, Connected Apps OAuth Usage, Deskwoot. Deleting your Deskwoot workspace disconnects Salesforce the same way first. Deskwoot's audit log keeps a record of each connection, which stays after a disconnect.

The Deskwoot package stays installed after a disconnect. If you no longer need it, uninstall it in Salesforce Setup under Installed Packages. Uninstalling alone does not end Deskwoot's access: Salesforce keeps it, and an access nobody revoked works again once the package is installed again. So disconnect in Deskwoot first. If the package is uninstalled while Salesforce is connected, Deskwoot notices within a day, ends its access and asks an administrator to connect again.

Troubleshooting

When the connect does not finish, the Salesforce page says why:

  • The Deskwoot package is not installed in this Salesforce org. Install it as an admin, then connect again.
  • Your Salesforce admin lets only approved users use the Deskwoot app. Assign the Deskwoot connection permission set to the user you sign in as and select that set in the app's policies (see Admin approved users), then connect again.
  • This Salesforce org or user has no API access. Check your edition (see Salesforce editions) and that the user has API Enabled, then connect again.
  • The Salesforce user you signed in as cannot read Contacts, Leads or Accounts. Assign it the Deskwoot connection permission set, then connect again.
  • Salesforce did not finish the sign in. Deskwoot connects production and Developer Edition orgs; a sandbox or a scratch org cannot connect yet. If your org does not let you sign in on Salesforce's login page, choose Use Custom Domain there. If your org uses login IP ranges, relax them for the Deskwoot app (see Login IP ranges). Then try again.
  • We cannot connect your Salesforce org just yet. Salesforce connections for new companies open again soon. Nothing was connected, and Deskwoot kept no access to your org. If you want to know when you can connect, write to hello@deskwoot.com.

Once connected, the Salesforce page can show:

  • Needs a new sign in: Salesforce no longer accepts Deskwoot's access, because the package was uninstalled, the access was revoked or unused for 30 days, or the same Salesforce user connected Deskwoot more than 5 times. Administrators get an email. If the package was uninstalled, install it again first. Then click Reconnect within 30 days of the date the page shows; after that Deskwoot removes the connection and the links between your contacts and Salesforce records, as a disconnect does.
  • Permissions missing: the user Deskwoot acts as can no longer read Contacts, Leads or Accounts. Check its permission set, then click Check now.
  • IP blocked: Salesforce refused Deskwoot because of the user's login IP ranges. Set IP Relaxation to Relax IP restrictions, then click Check now. You do not need to reconnect.
  • User not approved: the user is no longer among the approved users of the Deskwoot app. Assign it the permission set again, make sure the set is selected in the app's policies, then click Check now.
  • No API access: Salesforce turned off API access for the user or the whole org. Give the user API Enabled, then click Check now.

Recent problems on the Salesforce page lists the newest 10 things that could not be sent in the last 7 days:

  • This needs a linked Salesforce contact or Lead: link one. For a note or task your team added, then click Try again on its line in the conversation; a conversation log follows by itself when the conversation was resolved in the last 7 days.
  • The linked Salesforce contact or Lead no longer exists: it was deleted in Salesforce. Link another one. For a note or task your team added, then click Try again on its line in the conversation; a conversation log follows by itself when the conversation was resolved in the last 7 days.
  • Salesforce does not let Deskwoot see this person or The Salesforce user Deskwoot acts as cannot see this record: give the permission set View All Records on that object, or add a sharing rule for the user.
  • The Salesforce user Deskwoot acts as may not use a field or object: add it to the Deskwoot connection permission set.
  • Your Salesforce org needs a value on every new Lead: set one under Values for new Leads, and Deskwoot tries again the next time this person writes to you. When the line names no field, set the value, then add the person with Create Lead. For a value Deskwoot does not fill, ask your Salesforce admin.
  • Salesforce did not accept this, a value is too long or not allowed, or a validation rule refused it: the line names the field or the rule's message when it can. Change the value, or ask your Salesforce admin about the rule.
  • A duplicate rule blocks a new record for this person: link the person Salesforce has.
  • Salesforce already has a person with this email address, and your team said it is not this person: link the right one with Find person.
  • A Salesforce contact goes under the one account with exactly the company's name: add that Account in Salesforce, give the contact the right company, or use Create Lead instead.
  • Salesforce is no longer connected: reconnect Salesforce so Deskwoot writes there again.

Frequently asked questions

Does Deskwoot import my Salesforce records?

No. Deskwoot reads a person live while your team looks at them and keeps no copy of your Salesforce records. It stores which Contact or Lead belongs to which of your contacts, the Salesforce IDs of what it wrote there for 90 days, the org's name, ID and My Domain address, and the name, Salesforce username and ID of the user it acts as. New customers starts with the people who write to you after you connect.

Does Deskwoot change records in Salesforce?

No. It adds Tasks, Leads and Contacts, and updates only its own conversation log Tasks. It never changes a Contact, Lead, Account, Opportunity or Case Salesforce already has.

What happens when a Lead is converted to a Contact?

The section says that Salesforce converted the Lead and offers Link the merged record. Until your team clicks it, Deskwoot already writes new Tasks to the Contact the Lead became.

Why does Deskwoot not find a customer in Salesforce?

Deskwoot looks for the customer's email address, then their phone number, among the Contacts and Leads the user Deskwoot acts as can see. It never offers a converted Lead, only the Contact it became. If the contact in Deskwoot has neither, or Salesforce holds other ones, use Find person to search by name.

Can I connect a sandbox or a scratch org?

Not yet. Deskwoot connects production orgs and Developer Edition orgs. A Developer Edition org is a good place to try Deskwoot before you connect your production org.

How many of my org's API calls does Deskwoot use?

Showing a linked person in the Salesforce section takes 1 call, which Deskwoot reuses for 60 seconds. The lookup of new customers every 5 minutes takes 1 call for up to 100 people who wrote. Each write takes a few calls. The API budget card shows your org's use and sets how much of it Deskwoot's reads and background work may take.

Was this guide helpful?

Keep reading

Ask Fynn about this guide

Get a short answer from this guide and the rest of the help center.

Still need help?

Fynn answers from these guides in the chat, and you can reach the team there too.