What should an automatically logged call contain?
A useful activity tells the next rep when the call happened, whether anyone answered, what was discussed, and what was promised. A timestamp with “call completed” leaves most of that work unfinished.
HubSpot supports call activities with a timestamp, description, duration, direction and outcome. An association connects the activity to the CRM record. These fields are described in HubSpot’s Calls API documentation.
| Detail | DialSheet’s export |
|---|---|
| When and how long | Call timestamp, duration and direction. |
| What happened | The standard HubSpot outcome and exact DialSheet disposition. |
| What was said | Your notes, plus the AI summary when available. |
| What comes next | Available AI next steps, in the call body. |
| Where to continue | A link to the lead in DialSheet. |
The connector does not export audio or full transcripts. A note created outside a call becomes a separate note, rather than an invented call activity.
Match the contact before you send the activity.
Names are not reliable identifiers. Two contacts can share a name, and one prospect might use different spellings across your tools. DialSheet checks an exact email first, then verifies a full phone-number match.
For the first test, use a contact with the same email in both systems. If you use phone matching, include the country code. The contact must already exist in HubSpot; the initial connector does not create it for you.
If several records match, the activity pauses for review. Correct the record or add a unique email, then retry. A paused activity is easier to fix than a private call note filed under the wrong person.
Keep the specific disposition alongside HubSpot’s outcome.
A standard CRM outcome and a rep’s disposition answer different questions. “Connected” says a conversation happened. “Callback” says what to do next.
| DialSheet disposition | HubSpot outcome | Preserved in the body |
|---|---|---|
| Callback | Connected | Disposition: callback |
| Meeting booked | Connected | Disposition: meeting booked |
| No answer | No answer | Disposition: no answer |
| Left voicemail | Left voicemail | Disposition: left voicemail |
| Wrong number | Wrong number | Disposition: wrong number |
Your selected disposition takes priority over the AI suggestion. A completed phone connection alone does not prove a person answered, so the connector does not treat every completed call as Connected.
Run a first-call test you can verify.
- Create the same test contact in both tools. Use your own reachable phone number and the same email address.
- Connect from a Pro account. In DialSheet, open Settings → CRM integrations and authorize the intended HubSpot account.
- Make a new call after connecting. Save a distinct note and disposition so you can recognize the result.
- Check the HubSpot contact’s Activities tab. Allow the next scheduled sync run. Confirm the contact, timestamp, duration, note and outcome.
- Edit the note in DialSheet. Wait for another run and confirm that the same HubSpot call now contains the edit.
- Check the summary when it arrives. If the call has an AI summary, it should update the existing activity. There should still be one call record.
Native sync requires Pro, currently $29/month per seat. The connector starts with new activity after connection; old call history is not part of this test.
What to check when the activity is missing.
- The connection: confirm the correct HubSpot account under CRM integrations.
- The contact: confirm the email or complete phone number exists in HubSpot and identifies one contact.
- The timing: use a call or note created after the connection was established.
- The status: inspect the recent sync activity list. Fix the displayed problem before selecting Retry failed activities.
- The AI summary: check whether DialSheet has generated one for that call. The connector can only export context that exists.
A temporary timeout can leave uncertainty about whether HubSpot saved an activity. DialSheet searches for the original record before another create. Repeatedly disconnecting or recreating the connection is not a shortcut for this check.
For the connection’s exact scope, read the HubSpot integration page. For an assistant that reads call context and proposes follow-ups, see the DialSheet MCP server.