Eight action formats, with the tools to follow through.

The core response formats

Polls record preferences and plans organize possible dates or places. Bills calculate allocations from item claims, checklists record completion and challenges keep self-reported scores. Product decisions compare preferences without buying goods, contribution goals record non-binding pledges and mini quizzes ask one checked factual question.

Each format has a specific meaning. A progress bar does not verify a cause, a checkbox does not prove an external deliverable, and a product choice does not authorize payment. Write the audience, deadline and next step so recipients understand what the action can establish and which real-world process remains separate.

Planning and private collaboration

Dated plans add timezone-aware candidates, availability, RSVP, guests, capacity, waitlists, finite recurrence and calendar export. Private workspaces add roles, expiring recipient-bound invitations, discussion and responsibilities. The server checks permissions and shared owner-plan limits rather than trusting a hidden frontend button.

Saved templates reduce repetitive setup without copying participant responses. Drafts and scheduling let a creator prepare a request before publishing, subject to moderation and hosting jobs. Close or archive finished work with a specific handover. Existing records are not permission to bypass a downgraded plan or an expired membership.

Presentation, evidence and local assistance

Eligible branding adds a recognizable organizer, accessible accent and public logo. Locally generated QR codes and read-only public embeds provide alternate sharing routes. Analytics reports defined lifecycle events, with optional visits measured only after consent and exports scoped to authorized work.

Receipt recognition uses a bundled local worker and requires review before it fills a bill. The help assistant searches published sources without an external AI service. Optional provider-AI generation in the builder is separate, configurable and metered. None of these features can promise a perfect answer, a verified receipt or an unreviewed final decision.

An operator-controlled commercial service

Free, Pro and Team have editable finite allowances and feature entitlements. Paid personal accounts are excluded from platform ads. Billing can use direct Stripe or mapped WooCommerce products; automatic WooCommerce renewals require the subscription extension and a compatible gateway. Manual terms, cancellation and refund access changes remain explicit.

The operator also controls consent-based email, designed notifications, campaigns, automation, moderation, storage, backups, public content and advertising. These controls need actual provider configuration and staging checks. A configurable platform is useful because the operator can inspect and change its behavior, not because every external service is magically preconnected.

Illustrative workflow: one event, several focused requests

A group first uses a plan to compare feasible dates, then a checklist to prepare the agreed meeting. A product decision can shortlist an item the group might buy, while the authorized buyer separately approves the real merchant checkout. If the group later divides an actual receipt, a bill action records item claims and calculations without collecting participants’ money.

These requests can be linked without pretending one response format establishes every commitment. Private workspace roles control who may see or edit the work; finite plan allowances control capacity; a saved template reduces repeated setup. The assistant can find a relevant help guide, but cannot confirm a private order or make an account change. Keeping each request’s purpose visible produces a clearer handover than a single overloaded page. This is an illustrative combination of implemented controls, not a report of a customer or a guarantee of project success.

Before you share

1. Prepare: choose the response meaning and the appropriate audience.
2. Review: check actual evidence, permissions, capacity and the latest saved state.
3. Handover: name the next owner and keep external confirmations separate.

Make the next request clear.

Create an action ↗ · Read the detailed guide · Compare current plans