calltree

Heat-alert check-in calls for a town's register

Every name on the list, reached within the hour.

When a heat warning hits, Calltree phones every isolated elderly person on the town's register, asks three questions, and sends a human only to the ones who did not pick up or said something worrying.

No sign-up. 100 synthetic residents in Maryvale, Phoenix. Live on AWS: Lex, Polly, Lambda, Step Functions, DynamoDB, Amplify.

last drill · maryvale
98 / 100

Column height is how urgently a person is needed. Red is tallest.

61,672

people killed by heat in Europe in one summer. Most were old. Most died alone at home.

France has required every mayor to keep a register of vulnerable people and contact them during heat waves since 2004. American cities run the same thing with volunteers. Both take days. The people nobody reached are the ones who die. Nature Medicine, 2023.

16.2 million
Americans over 65 live alone. ACL, 2023
50%
of people on French heat registers were hard to reach in the 2025 heat wave. Only a third of social centres had enough staff. UNCCAS survey, 2025
600
outreach workers New York put on the street for wellness checks in July 2026, plus 150 new volunteers. NYC Emergency Management

Alert, call, decide, escalate, report.

  1. 1

    A heat warning

    EventBridge Scheduler polls the National Weather Service zone every 15 minutes. A new warning starts the campaign on its own.

  2. 2

    Every line rings

    Step Functions fans out eight calls at a time, retries anyone who did not pick up, and never skips a name.

  3. 3

    Three questions

    How are you feeling? Is your cooling working and do you have water? Do you need anything? Polly asks. Amazon Lex understands each answer with a confidence and a sentiment.

  4. 4

    Code decides, not a prompt

    OK needs three clear affirmatives. Anything on the never-OK list is urgent. Anything unclear goes to a person. 120 lines, unit tested, scored on 60 labelled calls.

  5. 5

    A person acts

    A neighbour is called for urgent cases, staff call back the unclear ones, a delivery goes to anyone without cooling, a visit is queued after two no-answers.

one call from the last drill · register r041 · attempt 1 · 43 s

  • 14:02:11

    calltree“How are you feeling right now? Any dizziness, or feeling unwell?”

  • 14:02:19

    rosa“I'm fine, just a bit light-headed.”

  • 14:02:24

    calltree“Is your air conditioning or a fan working, and do you have enough water to drink?”

  • 14:02:31

    rosa“The AC is on.”

  • 14:02:36

    calltree“Is there anything you need today, like water, ice, or your medication?”

  • 14:02:41

    rosa“No, I don't think so.”

Urgentnever-OK phrase · neighbour called at 14:03:19

The unhappy path, on purpose.

  • Q1

    resident“I'm fine, just a bit light-headed.”

    Urgent
  • Q2

    resident“What? I cannot hear you, the dog is barking.”

    Unsure
  • Q2

    resident“The AC has been broken since Tuesday, it is very hot in here.”

    Needs
  • ring

    line“no pick-up twice, home visit queued”

    No answer

It starts with fine. It is never OK. Nothing is guessed. No skipped rows.

What is real, what is not.

  • real Lex understanding, the rules, the escalations, the report, the NWS watch, the browser call in your own voice.
  • synthetic the 100 residents. No real person's data is on this register.
  • not yet the phone line. This AWS account is billed through AISPL, which cannot create Amazon Connect or Chime SDK numbers. The carrier is pluggable; a Twilio number attaches with three environment variables.

Where it is headed.

Mass-notification products send one-way alerts. Nobody knows who is actually alright. Calltree is the two-way layer: the same register and the same three questions, with a different trigger. Power shutoffs, where California utilities must reach medical-baseline customers and send a technician if they cannot. Floods. Boil-water notices. Wildfire smoke. Starting with heat, because heat already has a law and a register.