Introduction

Managani brings customer engagement, product growth, and guarded automation into one platform. Use the same site and customer identity across chat, feedback, public updates, onboarding, analytics, demand discovery, content, and lifecycle outreach.

What's Inside

Listen and Respond

Use Chat for live customer conversations and Feedback for requests, votes, comments, assignment, moderation, and AI-assisted triage.

Communicate Progress

Move approved feedback into a Roadmap, publish release notes in the Changelog, and notify subscribers when work ships.

Onboard and Engage

Run Surveys, guide users with Tours and Highlights, and deliver targeted Web Messages.

Learn and Grow

Connect Tracking and Customers, discover demand with Social Monitoring, and turn evidence into content with Content Strategy.

Automate Carefully

Use AI Automation for grounded chat assistance and rule-driven lifecycle outreach with rate limits, quiet windows, and human escalation.

Deliver Everywhere

Use the branded Widget and Portal, Desktop, MCP, or REST API depending on where the work needs to happen.

Next Steps

• Sites — Configure product surfaces and site settings
• Widget and Portal — Add customer-facing product tools
• Desktop — Install the native desktop app
• Settings — Manage account, team, tokens, search, and activity logs
• API Reference — Build integrations against the product API

Choose a Starting Workflow

For a new product, begin with a site, a widget deployment, and one customer-facing tool. Chat is useful when the immediate need is answering questions. Feedback is a better starting point when you need a shared record of requests that the team can review and prioritize over time.

For an established product, connect existing customer identity before launching targeted experiences. Surveys, tours, and lifecycle rules depend on knowing which customer is active and which actions that customer has performed. Review a sample customer's activity before enabling a campaign.

Choose a teammate to review incoming conversations or requests and another to maintain public progress updates. The same person can fill both roles in a small team. Keeping ownership clear helps prevent a published roadmap or automated message from drifting away from the work the team is actually doing.