NOMLY RECIPES

Give Ask Nomly a few things to always look out for.

Recipes are ready-made jobs Nomly runs for your restaurant. Each one checks the systems you connect, on a schedule or when something changes, then sends a brief, flags a problem, or asks before taking action.

Ask Nomly

Available

Ask Your Store

Text Ask Nomly a plain-language question about today’s store activity.

When you ask

Runs only after an authorized operator sends a question.

Reads: square

See how it works →

Morning

Pilot

Morning Owner Brief

A 7:45 AM heads-up with the numbers and loose ends that deserve attention.

Every morning at 7:45

Uses the restaurant’s local timezone and never sends inside configured quiet hours.

Reads: square, zendesk, gmail

See how it works →

Money

Pilot

Payout Watchdog

A quiet monitor for failed, delayed, or unexpectedly small payouts.

When a payout looks wrong

Evaluates verified payout records on a schedule and stays quiet when no threshold is crossed.

Reads: square

See how it works →

Money

Coming soon

Refund Spike Watchdog

Get a useful nudge when refunds break from the restaurant’s normal pattern.

When refunds materially spike

Planned threshold: minimum count and value plus a comparable-period baseline.

Reads: square

See how it works →

Money

Coming soon

Sales Pace Watchdog

Know when today is meaningfully behind a comparable day while there is still time to react.

At a configured checkpoint

Planned default: 2:00 PM local time, with absolute and percentage thresholds.

Reads: square

See how it works →

THE PRIVACY CONTRACT

Your restaurant, employee, and guest content does not train shared models by default.

Product improvement use requires an explicit organization opt-in. Recipes also show what they read and what they are never allowed to change.