Yekar.AI
Login

Keep people in control

Bound how long work can wait

Give pending decisions a clear operating window instead of leaving runs parked forever.

Talk to usRead the docs
Captured from the product Demo workspace
Choose how long an approval can wait before the run stops safely.

What this changes for your team.

Approval policy includes a timeout for unanswered decisions, with a 72-hour default. The pending record carries its deadline so workers and operators can treat expiry consistently even across restarts.

How it works in practice.

  1. 01

    Choose the response window appropriate for the agent's business process.

  2. 02

    When a gated call parks, calculate and persist its expiry deadline.

  3. 03

    Approve or reject before that deadline; otherwise the expiry policy closes the call.

What you can plan around.

The behaviour you can design against, stated concretely.

The timeout belongs to published approval configuration rather than an in-process timer.

Pending approvals persist across worker and application restarts.

The default applies when no custom timeout is configured and is not an automatic approval window.

Complete the operating path

View all capabilities
Keep people in controlNever turn silence into consent

Keep an unanswered write from becoming an external side effect simply because time passed.

Keep people in controlSend decisions to the accountable owner

Put approval with the person or team whose external authority the call will exercise.

Control who can do whatLet teams own their work

Separate workspace administration from the teams that author, run, and observe domain work.

Bring one real process

See how Yekar.AI fits the way you work.

Start with a job your team already owns, plus the tools and decisions around it.

Talk to us