> For the complete documentation index, see [llms.txt](https://documentation.movatic.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.movatic.co/admin-site/modes/sim-cards.md).

# SIM Cards

This guide is intended to provide operators with a comprehensive understanding of the SIM card technology utilized in these systems. While both systems use SIM cards, it's important to note that Omni Locks use "Super SIM," whereas Acton employs "Programmable Wireless SIM." Although the process for managing these SIM cards is quite similar, there are specific differences that will be outlined in this documentation.

**Key SIM Card Types**

* **Super SIM (Omni Locks):**\
  Super SIM is the type of SIM card used for Omni Locks. It's designed to provide robust connectivity across various networks, ensuring reliable communication between the lock and the system.<br>
* **Programmable Wireless SIM (Acton):**\
  Acton utilizes Programmable Wireless SIM, a versatile SIM card providing the necessary connectivity for the system to operate effectively. It's tailored to meet the specific requirements of Acton's system, optimizing performance and reliability.

Understanding and effectively managing SIM cards are essential components of ensuring the smooth operation of both Omni Locks and Acton systems.

##

## [Twilio Process for Activating SIM Cards](/admin-site/modes/sim-cards/twilio-process-for-activating-sim-cards.md)


---

# 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://documentation.movatic.co/admin-site/modes/sim-cards.md?ask=<question>&goal=<user_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.