AltoSignal Start free trial

Local delivery

Signals do not leave the building to cross the room.

Devices on the same office network now deliver signals straight to each other, at the same time as the cloud. Both paths carry every signal. When the connection drops, your team keeps signaling and there is nothing for anyone to do.

What this changes

Three things a practice manager can check off.

  1. 01

    Nothing to install in the office.

    It runs on the tablets and phones your team already knows how to use. No server in a back closet, nothing loaded onto clinic computers, and no IT project to schedule.

  2. 02

    One account covers every location.

    A practice with two or three offices runs all of them from the same account, with one place to manage staff, rooms, and channels.

  3. 03

    Signals travel locally and through the cloud at once.

    On typical office networks, a signal crossing the operatory takes the short trip instead of the long one out to a data center and back. If the connection drops, signaling keeps working.

Two paths, running at the same time

Every signal goes out both ways, on every send.

One copy goes straight to the other AltoSignal devices on your office network. The other goes through the cloud, the way it always has. Every device that should hear the signal hears it once.

Nothing watches for an outage and nothing switches over, because there is no switch to throw. The local path is already carrying the signal before anything goes wrong, which is why there is no delay to notice and no state for staff to be aware of.

Signals stay inside the practice's own network and are encrypted in transit.

What happens when the internet drops

Said plainly, because it is a trade and not a magic trick.

Keeps working

Signaling your team

  • +Sending a signal from any device on the office network
  • +Receiving it on the other devices on that network
  • +The buttons, rooms, and channels already on the board

Waits for the connection

Changing the setup

  • +Editing button labels
  • +Adding or removing a channel
  • +Reconfiguring the board layout

That is the honest shape of it. What clinical staff use every minute keeps working. What an administrator touches a few times a year waits until the connection is back.

Setting it up is nothing

There is no step here. That is the whole feature.

Devices find each other on the network by themselves. There are no fixed addresses to assign, no router settings to open, no server to stand up, and nothing to install on a clinic computer. Sign in on a device and it joins in.

Office networks do vary, and some configurations stop devices from discovering each other. On typical office networks it works with no setup at all, and the cloud path carries every signal either way.

Where it runs

The app takes part. The browser keeps doing what it always did.

Local delivery runs in the AltoSignal app on tablets, phones, and desktop. Those are the devices that hand signals to each other directly.

The browser version keeps working everywhere and still needs nothing installed, which is what makes it useful for a spare screen or a quick sign-in. It does not take part in local delivery, so a browser device receives through the cloud.

Practices used to have to pick one

Fast inside the building, or reaching past it.

Signaling software that lives entirely inside the office is quick and dependable for exactly that reason. It is also why it cannot reach a second location, why something has to run on site, and why it takes IT involvement to put in and keep going.

Signaling that lives in the cloud reaches anywhere and installs nothing. It also stops when the internet does.

AltoSignal now does both, from one account.

Put it in your own operatories.

Set it up on the screens you already own in under ten minutes. Cancel anytime, no phone call.

Start 30-day free trial

Want to see it running first? Follow one morning in a practice, front desk to operatory.