Shared Inbox Routing

HelpCrunch's shared inbox gathers messages from chat, email, and social channels into a single queue. When a new conversation lands, a Beam agent reads the message text, the sender's history, and any existing tags to work out the topic. Where the account's rule set names a clear action, such as a billing question or a password reset, the agent answers with the approved wording or assigns the conversation to the right teammate, then updates its status and tags. Conversations involving refunds, complaints, or anything the rules do not cover get flagged and handed to a person for review.

Contact Profile Updates

HelpCrunch stores a profile for every customer who reaches out, including past conversations, tags, and custom fields. When a conversation closes, a Beam agent reads the outcome and updates the contact's profile: adding a tag for the issue type, noting the resolution, or filling in a custom field the account has approved for automatic changes. This keeps the customer record aligned with what happened, without a teammate re-entering the same details by hand. Where the update would touch billing status, contract terms, or anything outside the approved fields, the agent leaves the profile untouched and notes the case for a person to update.

Knowledge Base Deflection

HelpCrunch links its knowledge base articles to the chat widget so customers can find answers before a conversation starts. A Beam agent reads incoming questions, checks them against existing articles, and where a strong match exists, points the customer to that article. If no article covers the question, or the customer replies that the article did not help, the agent stops there and passes the conversation to a support teammate instead of guessing at an answer. This keeps the deflection grounded in what the account has actually documented, not invented explanations of features nobody has confirmed.