> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/hardware-products/hardware/petroleum-devices/ruby/ruby2-quick-reference-guide/technical-support.md).

# Technical Support

## Verifone Technical Support Center

{% columns %}
{% column %}
**Help Desk Phone Number**

**Your Service ID**
{% endcolumn %}

{% column %}
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
{% endcolumn %}
{% endcolumns %}

## Information to Have Ready

Important information our Verifone Technical Support Center will need from you:

* Service ID.
* Description of the issue (include error message if applicable).
* What part of business is affected (POS, Pumps, DCRs, etc).
* If it is an issue outside, what type of pump/DCR is installed.
* Whether issue is ongoing or first occurrence.
* What was happening when the issue arose (do you know how to make it happen again)?
* Any steps already taken to resolve the issue before calling Verifone Technical Support Center.
* Local weather conditions during the issue and any recent power outages.

## Before Calling

Ideally, person making the call to the Verifone Technical Support Center:

* Is on site and prepared to work with agent.
* Has checked that all components of system are powered up.
* Can identify and locate Verifone hardware for troubleshooting.

{% hint style="info" %}
Visit our support website at support.verifone.com for manuals and general support materials. Also engage our support staff from this website via e-mail or online chat through the Petro and Convenience Support Channel.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.verifone.com/hardware-products/hardware/petroleum-devices/ruby/ruby2-quick-reference-guide/technical-support.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.