OpenAlly

Showing 25 of 26 from the live probe.

• Connect my OpenAlly account

  Start signing in to an OpenAlly account from this chat. Sends a sign-in request to the phones signed in to the account for the given email and returns a six-character sign-in code the person taps on their phone and later enters when they choose Connect. Never names a device and never says whether an account exists.

• Did my phone approve the sign-in

  Check whether the phone has approved a sign-in request started with start_sign_in. Returns pending, approved, declined or expired, and after approval the name of the device that approved it.

• What OpenAlly is

  A short, accurate description of OpenAlly for a given topic: overview, providers, privacy, platforms, business or apps. Static text from the app's own guide; needs no account.

• Search OpenAlly help

  Search the OpenAlly app guide for a question about the app: where a screen is, how to set something up, what a feature does. Returns up to five short excerpts with the guide slug to fetch next.

• Read an OpenAlly guide

  Fetch one section of the OpenAlly app guide by slug: app-guide, app-map, app-recipes, app-destinations, app-providers, app-skills-tools, app-aster, app-privacy-support. Start with app-guide, then the slug it points at.

• My OpenAlly account

  A one-glance summary of the connected OpenAlly account: when it was created, whether setup is complete, whether it has a plan, and how many devices are signed in when this connection may also see devices. No email, no ids.

• Has this account finished setup

  Whether the connected OpenAlly account has finished onboarding and has a working model selected, and which provider and model it uses. Use it before walking someone through setup.

• My OpenAlly plan

  The plan state of the connected OpenAlly account, in facts only: whether a plan is active, when the current period ends, what it includes in plain words, and credits left. Never prices, never a way to buy.

• Assistants connected to my account

  Every assistant currently connected to the OpenAlly account, with what each may access and when it was connected and last used. Disconnecting is done in the OpenAlly app under Profile, Security.

• My OpenAlly devices

  The devices signed in to the connected OpenAlly account: platform, app version, label, when each was last seen and whether it can receive notifications. Call it before any device tool; the device_ref values it returns are what those tools take.

• Send a message to my phone

  Send a short notification to the devices signed in to the connected OpenAlly account, or to one device by device_ref. The person sees it as a normal notification from OpenAlly.

• Open a screen in OpenAlly on my phone

  Send a notification that opens one screen of the OpenAlly app when tapped. screen_id must be an id from the app-destinations guide, exactly as written; some screens are Android-only and are refused for an account with no Android device.

• Send this page to my phone

  Send an https link to the devices signed in to the connected OpenAlly account, or to one device by device_ref, as a notification that opens the link when tapped. The link's host is shown in the notification. For a screen inside the OpenAlly app use open_app_screen instead.

• Ask the agent on my device

  Send a prompt to the agent running in the OpenAlly app on the person's device. The phone shows the prompt and the person approves or declines it there; the answer comes back here. Included with an OpenAlly plan. Waits up to 25 seconds; if the action is still waiting, check later with get_action_result.

• Check an action on my device

  Read the current state of a device action started by ask_device_agent or get_business_snapshot, by its action_id. Starts nothing new.

• Today's business numbers

  Today's counts from OpenAlly Business on the person's device: orders and bookings today, open orders, low-stock items. Counts only, nothing about customers, no money. The phone must be reachable; the person approves the read there. Included with an OpenAlly plan.

• Save a note to OpenAlly

  Create a note in the person's OpenAlly notes. It is stored in their account and appears in Notes on every signed-in device the next time it syncs, marked as added by this assistant.

• My recent notes

  The person's OpenAlly notes, most recently updated first, with a short preview of each. Use search_notes to find one by content.

• Search my notes

  Search the person's OpenAlly notes by words in the title, body or tags. Returns up to 10 with a preview and the note_ref to use with update_note or delete_note.

• Edit a note

  Replace the title, body, tags or pinned state of one of the person's OpenAlly notes. Only the fields given change; a field edited on a device at the same time keeps the later edit. Find the note_ref with search_notes first.

• Delete a note

  Delete one of the person's OpenAlly notes. It disappears from every device on the next sync. Ask before deleting; find the note_ref with search_notes first.

• Contact OpenAlly support

  Open a support ticket with the OpenAlly team as the person. Use it when the guide does not answer the question or something is broken. The reply arrives in the OpenAlly app under Support and can be read here with get_support_ticket.

• Check a support ticket

  The person's support tickets with their status and who wrote last, or one ticket by ticket_ref. Message bodies stay in the app.

• Reply on a support ticket

  Add the person's reply to one of their support tickets. With no ticket_ref, the most recently updated open ticket is used.

• Close a support ticket

  Close one of the person's support tickets. Replying later reopens it. Ask before closing.