Welcome
Create New Account
Login
Settings
Users & Controls
Email Notifications
Payment
Custom Fields
Tags
Activity
Lost Reasons
Profile
Contact
Enquiry/Lead
Company
Pipelines
Clients
- Clients
  How do I add a new client in Brexa?
  What information is necessary when adding a client (e.g., name, email, phone number)?
  How do I assign an owner to a client in Brexa?
  Can multiple users have ownership of the same client?
  What is the purpose of the client ID in Brexa?
  How can I view detailed information about each client (e.g., created date, owner)?
  Can I track interactions and activities associated with each client (e.g., meetings, emails)?
  Is there a history log of actions taken with each client?
  What actions can I take on clients within Brexa (e.g., schedule meeting, send proposal)?
  How do I prioritize actions based on client details and interactions?
- Client Projects
  How do I create a new project for a client in Brexa?
  What information is necessary when adding a project (e.g., name, cost, due date)?
  Can I track project details such as cost and due date in Brexa?
  How do I ensure accuracy and completeness of project information?
  What are the different project statuses available in Brexa?
  How do I update the status of a project as it progresses?
  How do I assign an owner to a project in Brexa?
  Can multiple users collaborate on the same project?
  What is the purpose of the project ID in Brexa?
  How can I view detailed information about each project (e.g., created date, owner)?
  What actions can I take on projects within Brexa (e.g., set milestones, track progress)?
  How do I prioritize actions based on project deadlines and milestones?
Set Up
Live Chat
Bot Chat
Messages
Teamchat
More

Powered by GitBook

How do I capture lost reasons for activities in Brexa?

PreviousLost Reasons NextWhat types of activities can have lost reasons recorded?

Last updated 27 days ago

On this page

In Brexa, lost reasons for activities can be captured by marking an activity as "Lost" and selecting or providing a reason for the outcome. This is typically done in the activity management section, where you can log why an interaction or task didn't achieve the desired result, helping to track and analyze unproductive activities.