Community Tutorials

Watch community-led walkthroughs that demonstrate Bento account setup and best practices.

Last updated: October 25, 2025

Note: This section is still expanding. Check back for additional community walkthroughs and transcripts.

Mark Szymanski · Account setup & first send

TL;DR summary (≈1 minute read)

  • Bento bundles email, SMS, chat, analytics, and automations in one platform.
  • Drag-and-drop and HTML editors let you customize templates, while deep segmentation targets the right audience.
  • Real-time chat, integrations with common form builders, and transparent pricing help teams ramp quickly.
  • Exceptional support—direct access to the team and community Discord—keeps onboarding personal.
  • Pricing scales with user count, and every plan starts with a 30-day free trial.

Text version highlights

Comprehensive feature set

Bento covers email, SMS, chat, analytics, and automations. Whether you are just starting or scaling, the toolchain adapts to your growth.

Integrations and customization

It plugs into popular form builders and commerce stacks. You can switch between a drag-and-drop or raw HTML editor and still stay on brand.

Automation & segmentation

Flows trigger off user behaviour or events so you can build sophisticated journeys. Advanced segmentation keeps the message relevant.

Built-in chat and analytics

Live chat is included, not bolted on. Dashboards provide attribution, funnels, and real engagement metrics to guide your next send.

Community & support

The Bento team—including the founder—hangs out in the Discord. You get quick answers, real feedback loops, and a user-driven roadmap.

Pricing

Plans scale with the number of users, not artificial feature gates. Try everything with a 30-day free trial before committing.


CreatorEgg · Forms, automations, and segmentation

TL;DR summary (≈1 minute read)

  1. Versatile form options – HTML forms, pop-ups, and surveys adapt to different lead-capture strategies.
  2. Advanced automation – Unique Flow builder allows complex, customizable sequences.
  3. Precise segmentation – Filter by custom fields, tags, and behaviour for targeted campaigns.
  4. GDPR compliance – Separate form submission from subscription to keep lists clean.
  5. WordPress integration – Quick setup for WooCommerce, LearnDash, and more.
  6. User-friendly UI – Intuitive design works for beginners and experts alike.
  7. Custom tracking – Detailed event tracking powers data-driven decisions.
  8. Fair pricing – 30-day free trial and no feature lockouts.

Text version walkthrough

So you want to try Bento without burning weeks learning the interface? This video compresses the essentials.

Forms

Bento offers HTML forms, pop-ups, and surveys. HTML forms cannot be saved, so copy the snippet into your site and keep a spreadsheet of event names. Avoid dropdowns and include a hidden $event_name field:

<form action="https://api.bentonow.com/v1/subscribers/{form_key}" method="POST">
  <input type="email" name="email" placeholder="Enter your email" required>
  <input type="hidden" name="$event_name" value="newsletter_signup">
  <button type="submit">Subscribe</button>
</form>

Automations

Bento splits automations across Sequences, Flow Emails, and Flows. Think of sequences as your email series, flow emails as the individual messages, and flows as the glue that connects triggers to actions. When a form is submitted, explicitly add the subscribe action—Bento will not assume it for you.

Segmentation

Target users by custom fields, tags, or behaviour. Surveys are perfect for collecting preferences and routing broadcasts only to people who said “yes” to hearing from you.

Compliance reminders

  • Track event names carefully so each form maps to the correct automation.
  • Use flows to tie everything together; forms alone do not change subscription state.
  • Keep segmentation rules lean and explicit so every campaign remains intentional.

Wrap-up

Bento feels different at first, but once you respect the event-driven model it becomes a powerful control panel. Start simple, confirm every trigger, and then build out more elaborate paths.

Edit on GitHub
Was this helpful?

Need the original Markdown? Open raw file