> For the complete documentation index, see [llms.txt](https://docs.milientsoftware.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.milientsoftware.com/help/moment-by-topic/integrations/known-issues/24sevenoffice.md).

# 24SevenOffice

## Customer number

By default Moment is the master for all integrations, when it comes to 24SevenOffice there are limitations on setting a defined customer number in 24SevenOffice.

As customers are created in Moment they will be getting the next available number in Moment. When the customer is then transferred to 24SevenOffice, a look up if this exists will be done. If the customer is not found - a new customer is created. The new customer will get the next available number at that time in 24SevenOffice (this might be different from the number given in Moment, if order of registering customers in Moment and 24SevenOffice differs.

In the log there will be a line that can look like this

```
Customers exported successfully: 54655 (24SevenOffice: Moment customerNumber 105750 is not the same as newly created company id 54655 so need to update Tibet customerNumber.);
```

The customer will be created, and in return the customer number in Moment is updated to what is set on this in 24SevenOffice.

Most of the time, this customer has at this time been included in an invoice in Moment. And on that first invoice sent the customer number will be the on given in Moment. Next invoice will have correct customer number as it is in 24SevenOffice.

We are looking into find a way to get around this, but due to limitations in the 24SevenOffice API, we need to put together a more advanced solution.


---

# 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.milientsoftware.com/help/moment-by-topic/integrations/known-issues/24sevenoffice.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.