> For the complete documentation index, see [llms.txt](https://help.solink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.solink.com/docs/get-started/introductory-guides/how-to-contact-our-team.md).

# How to Contact our Team

Reach out to our team via live chat, email or phone.

Still not finding what you're looking for here in the help center?

Our support and customer enablement teams are always ready to take your questions via live chat, phone or email. Use this page as a reference whenever you need to contact us.

You can contact us via the following methods:

* [Live Chat](#live-chat)
* [Phone](#phone)
* [Email](#open-a-ticket)
* [Book a Training Session](#book-a-training-session)

***

## Live Chat

A member of our Support team is always on standby to reply to a live chat message. You can initiate a live chat with us from the following Solink sites:

* [solink.com](http://solink.com/) (main website)
* [solinkcloud.com](http://solinkcloud.com/) (Solink platform)
* [help.solink.com](https://help.solink.com/) (Help Center)

Select the chat bubble at the bottom corner of any of these sites to initiate a chat. See the GIF below for a quick demonstration:

<img src="https://1562067156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMN1EUQcXYfv7FYpGJWR%2Fuploads%2Fgit-blob-b121ac2123b3dd2c3e3dc957f500db3ad703fa99%2F700c31d3bcc48403.gif?alt=media" alt="" width="560">

If you are using the Solink app on a mobile device, you can tap on the "speech bubble" icon near the top of the screen on either iOS or Android to navigate to our live chat page:

| **Android Live Chat** | **iOS Live Chat** |
| --------------------- | ----------------- |
|                       |                   |

***

## Phone

Use the following phone numbers to contact us:

**Support Phone**: 1-888-335-9844 (24/7)

* **Press 1** to speak with a Support agent
* **Press 2** if you are a technician doing supplementary work (for example, troubleshooting)
* **Press 4** if you are a technician performing a new Solink install

**Sales**: 1-888-817-6546

**Field Services**: 1-855-759-0609

**Reception**: 1-844-635-7305

***

## Open a Ticket

[Open a ticket with our Support team here](https://solink.com/contact-us/#ticket).

***

## Book a Training Session

You can book a 1-on-1 training session with a **Customer Success Manager** (CSM) from our **Customer Success** team if you require training on a specific Solink feature.

Our Customer Success team is comprised of several CSMs whose goals are to ensure you understand and get maximum value from Solink.

[Book a 1-on-1 training session](https://share.hsforms.com/1wtTSmJpgROiRIhEDWas-UA144dv?__hstc=63432176.2acc1ca27c2c5f759b7ab42fd1245806.1614606490465.1624464338692.1624557645348.132&__hssc=63432176.1.1624557645348&__hsfp=2028108962) with a Customer Success Manager.


---

# 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://help.solink.com/docs/get-started/introductory-guides/how-to-contact-our-team.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.
