> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# SASBOSS

> Set up and remove your clients' Access4 phone users, Microsoft Teams calling and phone numbers in SASBOSS from the ticket

SASBOSS is the portal Access4 partners use to sell and run hosted voice for their clients: Cisco BroadWorks extensions, Microsoft Teams calling, hunt groups, SIP trunks and the phone numbers behind them. Connect it once at the MSP level, and Neo works in every client enterprise under your partner account, through both SASBOSS APIs: the Provisioning API for clients, numbers, users and devices, and the Billing API for call records, invoices and charges.

## What Neo can do with SASBOSS

* Onboard a new hire: allocate a phone number to their client's site, and set up their Microsoft Teams calling, desk phone or extension with that number
* Offboard a leaver: suspend or remove their service, take back their phone, and keep their number for the next person or give it back to your account
* Add phone numbers to a client's site from your free numbers, and remove numbers a client no longer needs
* Change forwarding, schedules, hunt groups and call rejection; read call records, call centre statistics and a client's invoices and balance

## Onboarding and offboarding

Add SASBOSS to the agent that already handles your onboarding and offboarding tickets, and say in its instructions which service pack a new user gets, whether they get Teams calling or a desk phone, how you number extensions, and what happens to a leaver's number. Neo follows those rules first. Where they say nothing and the ticket does not say, Neo asks the technician, and it never guesses a service pack, a phone's MAC address or which number to give.

For Teams calling, Neo reads the new user's Microsoft account from Microsoft 365 and hands it to SASBOSS, which schedules the activation in the client's tenant. The client's Teams authorisation in SASBOSS must be done first.

## Each ticket stays with its client

Your SASBOSS login reaches every client enterprise under your partner account. On a ticket that names a company, Neo changes only records in the enterprise that company is mapped to: before it changes a site or a user, it reads the record and checks its enterprise. Reports across every client are for dashboards, chats and scheduled agents.

## Your enterprises are mapped to companies

Neo matches your SASBOSS enterprises to the companies in your PSA and keeps the mapping on the SASBOSS card's **Organization Mapping** tab, refreshed on each PSA metadata sync. A ticket's agent then works in its client's enterprise.

Matching uses the enterprise's name: exact, then after stripping a legal-form suffix (Ltd, Inc, LLC). Last comes an AI match for the long tail.

**A name that matches exactly one of your PSA companies, as it is or after stripping a legal-form suffix, or a match you confirm, is handed straight to your agents.** An AI match waits for you on the Organization Mapping tab, and so does a name two of your PSA companies share, or two enterprises that match one company. Confirm or correct each there.

Anything Neo could not match stays unmapped and visible on the same tab, where you can set the right company by hand. A mapping you set by hand survives every later sync.

See [SASBOSS API](https://docs.neoagent.io/agents/tools/communication/sasboss-api.md) for the permission groups.

## Next steps

> **[Connect SASBOSS](https://docs.neoagent.io/integrations/sasboss/connecting-to-neo.md)**
>
> Get Neo's IP addresses whitelisted, make an API login, and save it in Neo.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.