Automation
Use Home, the activity feed, and Business Rules
Review what Kluck has done, resolve items that need attention, and manage rule-driven work.
Use Home as your operating inbox
Home brings together Routine runs, flagged issues, and competitor updates, including items that need a decision. Issue cards may come from Business Rules or show as Store Ops. Use Home to understand what changed since your last visit. The page is reachable after onboarding even with no connectors; without Shopify or Meta the feed asks you to connect instead of showing activity.
- Filter by Issues flagged, Routines ran, or Competitor updates to focus the feed.
- Review status, severity, source, and time before acting.
- Open an item for its full context.
- On Home, choose Review with Kluck or Mark as seen when those actions appear. Rerun or edit Routines when available.
- Use the Business Rules board for Approve, Discuss, or Dismiss on rule cards.
Manage Business Rules
Business Rules organizes rule-driven work into To Do, In Progress, and Done. A rule can be evaluated, discussed, approved, dismissed, or moved as its status changes. Open the board from a rule card on Home, or go directly to /business-rules; it is not a separate main navigation item.
- 1Open a Business Rule card from Home, or navigate directly to the Business Rules board.
- 2Review the To Do column for new evaluations.
- 3Open a rule and inspect its evidence and proposed next action.
- 4Choose Approve, Discuss, or Dismiss when those actions are available.
- 5Drag cards between To Do, In Progress, and Done as work progresses.
- 6Use Run Evaluation to check the rules now, or Clear Board when you intentionally want to remove the current cards.
- 7Use Home to follow later activity created by the rule.
Current notification scope
Treat the in-app Home feed as the confirmed source for rule and routine activity. Do not rely on email, SMS, Slack, or push delivery unless Kluck explicitly shows that channel as configured.
Still need help?
Send the team a useful support request.
Include the workspace, affected feature, what you expected, and the error you saw. Never include passwords or access tokens.
Contact support