> For the complete documentation index, see [llms.txt](https://help.smartrr.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.smartrr.com/docs/support/integrations/blueprint-x-smartrr-integration.md).
# Blueprint x Smartrr Integration
The Blueprint x Smartrr integration allows customers to manage their subscriptions via SMS.
Smartrr's integration with Blueprint works by sending automated SMS for upcoming subscriptions, subscription confirmation, and post-order check-ins. These messages can be used for the following use cases:
* Welcoming new subscribers
* Letting a subscriber know when their next shipment is upcoming
* Allowing customers to SKIP or DELAY via SMS response
* Resolving issues with delayed shipments or product questions
## Setup
First, you'll need to generate a unique access token in the Smartrr App for Blueprint. Log into your Smartrr admin and navigate to **Integrations**. Under the **API Keys** tab, select **Create Key**.
We suggest naming your Token Nickname and Application Nickname "Blueprint". Before creating, ensure you change the permissions for Subscriptions, Customers, and Webhooks from Read to **Read and Write**. Press **Create** and then copy your newly created key.
In your Blueprint admin, navigate to your Integrations Hub and click **Smartrr Subscriptions**.
Paste your copied key from the Smartrr Admin into the field labeled **Smartrr Access Token**. Click **Test connection** and wait for the green tick to appear. Next, click **Activate** to complete integration setup.
## SMS Subscription Management
To set up some of the use cases discussed at the beginning of this article, navigate to the Automatics section of your Blueprint admin. Toggle live (or create) the relevant subscription automations.
* [New Subscription](https://help.blueprint.store/create-a-subscription)
* [New Subscription Check-in (1st order only)](https://help.blueprint.store/create-a-subscription-post-order-check-in)
* [Upcoming Charge](https://help.blueprint.store/create-an-order-confirmation-message)
* [Recurring Charge Confirmation](https://help.blueprint.store/create-a-recurring-charge)
{% hint style="info" %}
**Note:** By default, Smartrr sends upcoming subscription charge messages 3 days before the upcoming charge. Currently, this time frame can't be change.
{% endhint %}
❓ Have more questions about Blueprint? Check out their [Help Center](https://help.blueprint.store/).
---
# 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://help.smartrr.com/docs/support/integrations/blueprint-x-smartrr-integration.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.
