> For the complete documentation index, see [llms.txt](https://prosbcdocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosbcdocs.telcobridges.com/telecom-references/developer-reference/caf/services.md). # Services A service is the sum of all the classes offering a high level functionality to the caller. When a caller reaches the system, several services may be offered depending on the calling number, the called number or any other criteria. Such services maybe be conferencing rooms, chat rooms, call-bridging, voicemail, or any other service. Toolpack already provides source code for some reference services such as call-bridging and voicemail. Those services are built upon Toolpack and uses all the building block to provide the service. ### Usage When an incoming call reaches the system, the application chooses the appropriate service for this call leg. Then the application creates the service by instantiating the proper service class, and then assigns the call leg to the service. Here are some reference services provided by Toolpack: * [CallBridging reference service](/telecom-references/voice-and-media/bridging-service.md) * VoiceMail system reference service *** Return to the Toolpack [User Guide](https://prosbcdocs.telcobridges.com/tmedia-documentation/other-pages/getting-around-the-portal/user-guide) --- # 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://prosbcdocs.telcobridges.com/telecom-references/developer-reference/caf/services.md?ask=&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.