CALL-E

HungryCall

Find a delivery. Stay on budget. Set your delivery, budget and food preferences. HungryCall checks restaurants in order and stops when one confirms a match.

Built by ellmos-ai with CALL-E.

Try the demo Watch author demo

The public demo uses saved responses. It cannot place calls.

Delivery, within your budget.

Fictional scenario · simulated calls

The fictional brief requires delivery with a maximum total price.

Original conceptual demonstration with fictional people and saved sample responses. No real call, message, booking, order or delivery is made.

Read the narration

Set a budget and require delivery. One restaurant costs too much. The next cannot deliver. The third restaurant meets both conditions. Keep the match and stop calling without placing an order.

Try it yourself.

Change the budget, then inspect one saved restaurant response at a time. The sequence stops at the first match.

Interactive mock · state stays in this page and resets on reload.

Delivery required to a fictional address. Restaurant responses are fixed samples; your budget changes the decision.

Ready to explore.

Review the sample settings, then start the simulation.

    0 simulated calls

    One brief. One match.

    You define the conditions once. HungryCall checks candidates in order and stops after one restaurant confirms a match.

    1. Set the conditions

      Enter the location, food preference, delivery requirement and maximum total price.

    2. Call candidates in order

      CALL-E asks one restaurant at a time about delivery, total price and estimated arrival.

    3. Stop on a match

      After a restaurant confirms a match, HungryCall ends the sequence without calling the remaining candidates.

    One match, with a reason for each decision.

    Illustrative restaurant sequence. The public demo uses saved responses and places no calls.

    Trattoria
    Over budget. Continue to the next candidate.
    Burger House
    No delivery. Continue to the next candidate.
    Asia Wok
    Match found. End the sequence.
    Sushi Kudo
    Not called.

    Try your own search brief.

    Open the simulated demo, set your delivery and budget requirements, then follow each restaurant’s response through to a match.

    Open the demo

    Build around clear rules.

    Use this when one successful candidate is enough: restaurant reservations, appointment searches or local supplier checks. Keep the candidates, conditions and reasons for continuing visible to the person making the request.

    • Define the requirements. State what must be true, such as delivery to the requested address.
    • Set a hard boundary. Use a maximum total price or another explicit limit.
    • Keep the outcome. Record the result and why a candidate was accepted or rejected.
    • Review ambiguous outcomes. An uncertain agreement needs review before another business is called.

    To place real calls, run and configure your own deployment using the author’s setup guide. The simulated demo lets you explore the decisions; it does not place an order.

    Explore the calling flow.

    Try the simulated demo, then inspect the implementation.

    Try the demo View source

    HungryCall is maintained in ellmos-ai/hungrycall. CALL-E maintains this case guide. The illustrations are conceptual; they are not product screenshots or call records.