> For the complete documentation index, see [llms.txt](https://api.bind.hr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://api.bind.hr/messaging-api/guidelines.md).

# Guidelines

## The Importance of Using SMS Templates

At Bind, ensuring the security and integrity of our messaging services is a top priority. To protect end-users from unsolicited messages, scams, and smishing attempts, we require the use of pre-approved SMS templates for all outgoing messages.

### Why Templates are Required

The primary reason for this policy is to create a safe and trustworthy messaging environment. By validating every template, we can significantly reduce the risk of malicious content reaching telephone numbers. This process helps us ensure that all communications sent through our platform are legitimate and expected by the recipient.

### The Template Approval Process

To maintain these high standards, all SMS templates must go through a validation process before they can be used:

1. **Submission:** Clients create and submit their SMS templates through our API
2. **Validation:** The Bind team carefully reviews each submitted template to ensure it complies with our security standards and does not contain any potentially harmful or unsolicited content.
3. **Approval Notification:** Once a template is approved, the client will receive an email notification confirming that the template is ready for use.

Only after a template has been successfully validated and approved can it be used to send messages to your audience. This ensures that every message sent from our platform is secure, compliant, and trustworthy.


---

# 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://api.bind.hr/messaging-api/guidelines.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.