Roadmap

- Create app using a framer like Capacitor or alternative.
- Get verified with Apple Developer Account and Google App Store.
- Publish

New action: Add Contact to Workflow.
- Chain workflows by adding contacts to other automations.
- Use case: Automatically enroll a customer in a long-term maintenance reminder workflow immediately after their "Job Complete" automation finishes.

New Action: Create, find, update, and delete Visits. Retrieve a Visit into context by searching for it by: Customer (accept customer record or passing in a string), visit scheduled date, servicing technicians (find by selecting technician record or passing in string).

Add Contact Fields to the Create Contact Action
- Be able to assign users
- Be able to set address
- Be able to set the source/campaign source/etc

Draft and Publishing: An automation should not be published be default, meaning it won't pick up the trigger and run the automation. Think of it like an off/on switch. Create a toggle switch for draft/publish in the automation datagrid and automation edit.

Automation Enrollment and Execution History: Each automation should log enrollment and execution. Enrollment tracks what users were added to the automation and when. Execution tracks which steps were executed, the subject of the action, and what the results of the action are.

Folders: Folder functionality should be added to like automations can be grouped together. Use case: A user wants all Quickbooks-related automations to be in folder 'Quickbooks`.

Other tweaks: Combine the Create & Update.

- Allow users generate, send, collect, and store signed agreements from Contacts.
- Requires settings to control if a Quote can be moved forward without a signed agreement.
- Controls for creating agreements and requesting a signature should be from the Quote.
- Create Contract templates in Settings > Templates

Use case: A pest control company wants to enforce a minimum contract length and cancelation policy, but they require a signature from the customer acknowledging their terms.

Statistic tracking for forms: Track form views, starts, and submission counts.

Form security: Add reCAPTCHA to forms to reduce fake/malicious submissions.

Multi-step Forms: Multi-step embeddable forms that slide between steps instead of one large, static form. Multi-step forms reduce interest-to-lead friction by hiding how many inputs they have to fill out before getting the end result. This also allows for capturing as much lead data as possible in case the lead stops filling out the form half-way through.

- Basically soft deletes. A contact must be archived before it can be permanently deleted.
- Contact grid should have controls to show archived contacts
- Archived contacts should be removed from workflows and activate DND for outbound messages through Conversations.

- App controls for creating referrals.
- Backend system for tracking who-referred-who and incentives for referrals.
- Billing system works with referral system for incentives (For example, x month(s) free if you refer someone and they sign up)

This feature will allow users to create mobile profiles that change how different roles and users can access features from the mobile app. Mobile profiles control what tools are immediately accessible from the mobile menu.

This feature is useful when you have multiple mobile users, but you want the app to behave differently depending on the role they fill. For example, the mobile menu for a sales representative would have tools like the quote builder, sales map, schedule, and conversations, while the service technician's bottom bar would have their schedule, clock-in/out, leaderboard, and policy/checklists.

- Mobile profiles are created in settings
- Mobile profiles are assignable from its settings page
- Mobile profiles are assignable from any user edit or role edit page.

- Visible from dedicated Stats page
- Load this page in Map > Roster
- View your own stats and your team's stats.

Example stats that teams want to see:
- Individual technician stats: revenue serviced by day/week/month, average time on site, average ticket, total upsells, average upsell amount.

- Sales rep stats: revenue sold by day/week/month, conversion rate, average ROI

For now, emails for reminders, receipts, etc should be handled by Crewvana entirely.

The user will have little-to-no control unless SMTP support is added, which allows for sending/receiving emails from the Conversations tool using their custom domain. (Or Crewvana can be the domain middleman)

- Create quote template, generate quote from template, and send quote to customer.
- Customers can accept the quote
- Automation triggers for "quote sent", "quote viewed", and "quote accepted"
- Automation actions for "send quote", and "update quote" (edit fields, cancel quote, mark as accepted)
- Quotes have a unique URL:

Option A: quotes.subdomain.crewvana.com/quote/<quote_id>
Option B: subdomain.crewvana.com/p/quotes/<quote_id>
('p' indicates portal. Portal indicates customer context)

Invoices
- Invoices are A FORM OF COLLETING PAYMENT. Created from a JOB being completed OR MANUALLY CREATED FROM A QUOTE.
- See statuses, filter, and act on invoices.
- Invoices can have have billing terms (default to due on receipt, 14 days, 30 days, custom)

⚠️ Minor Observations for Verification:
While the functionality is there, I noticed two small areas where the implementation deviates slightly from your exact wording:

Filter Wording: The top bar filter currently uses the labels "Sent (Outbound)" and "Received (Inbound)". It should say "Sent to <endpoint>" and "Received from <endpoint>".
Event Consolidation: Currently, a call produces two events in the feed: an initial "Incoming Call..." (status: ringing) and a separate outcome event when the call ends (status: completed/failed). The CommEvent's status should change. (Updating a single record rather than creating a second one.)

The following should happen on inbound and outbound phone call:

- A contact should be created for the endpoint if none exists.
- A conversation should be created if none exists.
- CommEvent for the call should be created and show in the conversation feed.
- The CommEvent's status should change depending on call outcome. (Answered, missed, failed)
- The tenant and contact's Do Not Disturb settings should be enforced (if a customer opts-out, the call should fail automatically through Twilio)

For inbound calls, the following should be enforced:
- Route the call to the selected user(s) webapp or phone number.
- If routing to the webapp, the mobile app should also ring and be treated as a phone call from the Twilio number. (Call merging where the Twilio number acts as the middleman)
- Notifications for incoming call and missed calls.

Other Notes:

- Phone calls must persist if the page refreshes. Previously it was hanging up on page refresh.

UI requests:

- Right sidebar should show contact information and tools.
- Top bar should have functioning controls to star, toggle read status, and filter.
- Top bar filter should have dropdown menu filter to only show CommEvents that are messages, voicemail, phone calls, emails, sent from endpoint, sent to endpoint.

- Added a page for agentic and generative AI to learn about Crewvana.
- Accessible at https://crewvana.com/llm-info

- Added checks for duplicates by phone, email, etc.
- Added controls for duplicate merging, including an "ignore duplicate" feature.
- Refactored the contact import tool to provide different options for handling duplicates.

- Supports viewing schedules for multiple users and overlapping appointments.

- Collect business operating hours in Business Settings page (Checkboxes for each day of the week with open-close time)

- Allow business to mark as closed for holidays. (Suggest Christmas, Thanksgiving, 4th of July etc) Affects the calendar page visuals on holidays to schedulers don't mistakenly book jobs on holidays.

- Calendar should reflect business hours (instead of 12am-12am) and visually block off holidays, but still allow scheduling.

- Mobile users: must be saved to home screen for notifications to work properly.
- Added a workflow action to send notifications

Allows users to trigger workflows when a tag is added and/or removed from a contact.

- Created a settings page to manage contact tags

- Allows finding customer by phone number, name, and email address.