Skip to content

Integration guide

Give Hermes a persistent company SMS identity

Use Hermes to complete an authorized company-account SMS step, with a stable number and a clear handoff when the task needs a person.

Install through Hermes' skill manager

Install and confirm the Phonekit skill in HermesShell
hermes skills install https://www.phonekit.io/.well-known/agent-skills/phonekit/SKILL.md
hermes skills list --source hub

Hermes supports direct skill URLs and scans community installs. Its skills documentation explains discovery, inspection and updates. Invoke /phonekit in a Hermes session after confirming installation.

Connect the runtime that performs the task

Run the CLI connection in Hermes' actual execution environment. A gateway or remote worker needs Node and its own selected-number credential; a login performed on your laptop does not configure that worker.

Choose the number assigned to the company account and record its label with the task. Keep the account's service role and permitted actions in the instructions.

Delegate an invitation with a finish line

Accept the intended company invitation
Use /phonekit for the Product operations number. Complete the SMS invitation for the company workspace I named, using the existing authorized browser session. If the invitation is already received, check its receipt time and intended service. If we request a new message, mark first and wait at most 120 seconds. Open only the expected invitation link and confirm membership in the intended workspace. If another approval is needed, stop at that step and report it without the link or code.

Illustrative task report

Account: named company workspace · Outcome: invitation accepted and membership confirmed · Follow-up: administrator review, if the service requires it

Keep continuity in the account record

Hermes may return to the task in another session. Store the number assignment and completed account action in your normal account inventory. For another receive attempt, capture a new position before its send. For scheduled work, the assistant's host owns scheduling; a bounded Phonekit read finishes each attempt.

Use the agent task contract when defining unattended responsibilities.

Questions you may have

Why can the chat see the skill but not run Phonekit?

The skill supplies instructions; the execution worker also needs Node, command access, network access and a Phonekit credential. Inspect that worker rather than assuming the messaging interface runs the tool locally.

Can Hermes keep watching a number?

Hermes can schedule tasks according to its own capabilities and configuration. Each Phonekit receive call is bounded. Define what the scheduled task may do, which receipts it should inspect and when to request a human decision.

Can I share an operations number with another assistant?

You can deliberately scope connections to the same number. Avoid overlapping verification requests without correlation. Separate numbers or serialized account actions keep message ownership clear.

What should a handoff contain?

Include the company account, number label, completed stage and next decision. Keep credentials and short-lived invitation or verification values inside the intended task tools.

Use a number in your next task

Bring the account or test flow your assistant needs to complete.

Explore agent workflows