Questions about Pulse? Here are the straight answers.

It builds and updates Salesforce reports from a conversation. Ask for something like “Show pipeline by stage,” review the setup, and Pulse creates the report and charts in Salesforce.

No. Describe the result you want in your own words. Pulse handles the fields, filters, formulas, groupings, and charts.

Yes. Search your existing Salesforce reports by name or folder, open one next to the chat, and describe the change you want.

When you connect Salesforce, Pulse reads the fields and choices available to your user, including custom fields. It checks that setup before building the report.

Every number comes from a Salesforce query. Open “How this was calculated” on a chart to see the query and its source report.

No. Your Salesforce permissions still apply. If Salesforce won’t show your user a record or field, Pulse can’t see it either.

No. It can create reports, dashboards, and formulas inside reports. It can’t edit records, fields, users, permissions, flows, or automation.

Public links are off until you enable one. Anyone with an enabled link can view the approved aggregate snapshot, but not detail rows, Salesforce IDs or links, source fields, filters, Boolean logic, formulas, or your original request. Disabling permanently revokes that URL; enabling again creates a fresh one.

Usually a few minutes the first time. A Salesforce admin installs Pulse’s metadata-only OAuth registration once for the org; then each user signs in through Salesforce and approves the connection.

Yes. Disconnect inside Pulse whenever you want, or remove the connection directly from Salesforce.

You can connect a production org or sandbox with Salesforce API access.

It’s $120 per month for one connected Salesforce org and includes 100 customer-written messages. Pulse replies, presented choices, approvals, and the Salesforce reports or dashboards created from a message do not cost extra.