> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/helpdesk-integrations/hubspot/troubleshooting.md).

# Troubleshooting

Fix a missing Screendesk card, the card's messages, and recordings that don't reach the ticket.

## The Screendesk card is missing

Check that the app is installed in the HubSpot account you're looking at, and that the **Screendesk** card is in the sidebar layout your team uses (**Settings → Tools → Inbox & Help Desk → Help Desk**, **Sidebar customization** tab). Then reload the ticket.

## The card shows a message instead of its actions

* **You're not in this Screendesk workspace**: no workspace connected to this HubSpot account has a member with your HubSpot email. Ask an admin to invite that exact address.
* **Accept your Screendesk invitation**: Screendesk emailed you an invitation. Accept it, then click **Try again**.
* **HubSpot isn't connected to Screendesk**: the workspace was disconnected from this HubSpot account. An admin connects it again in **Settings → Integrations**.
* **HubSpot needs to be reconnected**: HubSpot stopped accepting Screendesk's access, so recordings no longer reach your tickets. An admin reconnects it in **Settings → Integrations**.
* **Two Screendesk workspaces use this HubSpot account**: you're a member of both, so Screendesk can't tell which one the ticket belongs to. An admin disconnects HubSpot from the one you don't use.
* **Your Screendesk role is view-only**: **Watch only** members can't request or share recordings. Ask an admin for a member role.

## I clicked an action but nothing was sent

That's expected. The card copies a link: paste it into your reply and send it.

## A customer sent a recording but the ticket has no note

1. Check that the customer submitted it, not only stopped recording, and that it's in the right Screendesk workspace.
2. Check that the link was copied with **Request a recording** on this ticket. A link from a snippet, a marketing email or a form never adds a ticket note: the customer pastes the recording's link back instead. A chatbot's recording goes on the customer's contact. A link from another ticket adds the note there.
3. Check that the ticket still exists, and that the card doesn't say **HubSpot needs to be reconnected**.

If it still has no note, contact support with the ticket and recording references.

## Start a video call is missing

Video calls need a Pro or Enterprise plan and a role that can host calls. Without them the card doesn't show the action.

## Chatbot or Breeze problems

See [Chatbots and Breeze](https://docs.screendesk.io/helpdesk-integrations/hubspot/chatbots-and-agents.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.screendesk.io/helpdesk-integrations/hubspot/troubleshooting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
