Planned
Tasks — Improvements & Enhancements
We're collecting all feedback related to the Tasks feature in one place. If you have a request, improvement idea, or workflow frustration tied to Tasks, please comment below or upvote this post. Examples of what we're tracking: Task creation and assignment improvements Due date and reminder behavior Task visibility across Jobs, Leads, and Contacts Filtering, sorting, and list management Notifications tied to tasks Mobile experience for task management Any other Tasks-related workflow gaps Your feedback helps us prioritize what gets built. Drop your use case in the comments so we understand the full picture. Internal Tags (for your reference): tasks daily-operations workflow placeholder
Jeremy harrison About 21 hours ago
💡 Feature Requests
Planned
Tasks — Improvements & Enhancements
We're collecting all feedback related to the Tasks feature in one place. If you have a request, improvement idea, or workflow frustration tied to Tasks, please comment below or upvote this post. Examples of what we're tracking: Task creation and assignment improvements Due date and reminder behavior Task visibility across Jobs, Leads, and Contacts Filtering, sorting, and list management Notifications tied to tasks Mobile experience for task management Any other Tasks-related workflow gaps Your feedback helps us prioritize what gets built. Drop your use case in the comments so we understand the full picture. Internal Tags (for your reference): tasks daily-operations workflow placeholder
Jeremy harrison About 21 hours ago
💡 Feature Requests
Planned for V2
V2 Notifications System Overhaul
V1 Notification Settings is a flat, company-level toggle list (New Appointment, Proposal Accepted, Proposal Rejected, Proposal Viewed, Invoice Viewed, Invoice Sent, Chat Message Received) with no channel selection, no per-user preferences, no in-app notification center, and no delivery history. Enhancement Ticket — V2 Notifications System Overhaul Ticket Type: Enhancement Target Version: V2 Status: Placeholder — Pending Discovery & Scoping Priority: TBD Area: Notifications / Settings / User Experience Summary The current V1 notifications system is a flat list of on/off toggles scoped to the company account level. It provides no delivery channel selection, no per-user preference control, no in-app notification inbox, and no notification history. This ticket captures the full scope of known V1 gaps, FeatureBase user requests, and PM roadmap items that should be addressed in the V2 notifications overhaul. This is a placeholder intended to anchor discovery, scope definition, and design decisions before active development begins. User Story As a DripJobs user (owner, admin, or team member), I want a notifications system that gives me meaningful, timely, and personalized alerts about the events that matter to my role, delivered through the channels I prefer, so that I never miss a critical business moment and am not overwhelmed by irrelevant noise. Business Rules (Functional Requirements) 1. Notification Categories & Event Coverage The V2 system must support notifications across all major workflow areas. At minimum, the following event categories must be represented: Proposals & Estimates Proposal sent to customer Proposal viewed by customer Proposal accepted Proposal rejected / declined Proposal expired (if expiration logic exists in V2) Counter-signature completed Appointments & Scheduling New appointment created Appointment confirmed by customer Appointment rescheduled Appointment cancelled Appointment reminder (pre-appointment) Jobs & Work Orders Job created from accepted proposal Work order sent Work order viewed Job status changed Job marked complete Invoices & Payments Invoice sent to customer Invoice viewed by customer Invoice paid Invoice overdue (if applicable) Deposit received Payment failed or declined Communications New chat message received (DJ Chat / in-app messaging) New inbound SMS received (if Text Messaging add-on is active) New inbound email reply received Leads & Pipeline New lead created (manual or via integration) Lead assigned to a team member Deal stage changed Deal archived or lost Team & Internal Task assigned to a user Task completed Mention or tag (if V2 introduces @mentions) New team member added to account Automations (Drips) Drip sequence enrolled Drip step failed to send Drip sequence completed 2. Delivery Channels The system must support multiple notification delivery channels. Each notification event must be configurable per channel independently: In-App (Notification Center) — persistent, visible within the DripJobs app Email — sent to the user's account email address Push Notification — mobile push via iOS and Android apps SMS — optional channel; must only be available if the account has the Text Messaging add-on active 3. Notification Preferences — User-Level Control Each individual user on an account must be able to configure their own notification preferences independently. Company-wide defaults may exist, but individual users must be able to override them for their own account. Preference controls must allow a user to: Enable or disable a notification event entirely Select which delivery channels they want for each event (e.g., in-app only, email + push, etc.) Set quiet hours during which push and SMS notifications are suppressed Account owners and admins must be able to: Set company-wide default notification preferences that apply to new users on the account View which users have notifications enabled for critical events (e.g., invoice paid) Optionally enforce certain notification types so individual users cannot disable them (e.g., payment received) 4. In-App Notification Center V2 must include a persistent in-app notification center (notification inbox/bell) that: Displays a real-time count of unread notifications Shows a chronological feed of all in-app notifications Allows users to mark individual notifications as read or mark all as read Allows users to dismiss or clear notifications Provides a direct link from each notification to the relevant record (proposal, job, invoice, deal, etc.) Persists notification history for a defined lookback window (open question — see below) Distinguishes between read and unread states visually 5. Notification Content & Formatting Each notification must include sufficient context for the user to understand and act without needing to navigate elsewhere first. At minimum, each notification must include: The event type (e.g., "Proposal Accepted") The customer name and/or company name The relevant record name or identifier (e.g., proposal title, job name, invoice number) A timestamp A direct action link to the affected record Notifications must not expose sensitive financial data (e.g., full payment amounts in push/SMS) beyond what is appropriate for the channel. 6. Role-Based Notification Relevance Notification events should be scoped to the user's role where applicable. A field technician should not receive notifications about invoice payment events unless their role warrants it. An admin or owner should receive account-level alerts that a standard user would not. The system must support role-aware defaults while still allowing individual user overrides. 7. Notification Grouping & Digest (Future Consideration) For users who receive high notification volume, the system should support notification grouping or a digest option. For example: Group multiple "Proposal Viewed" events from the same customer into a single notification rather than firing individually Provide a daily or weekly summary digest option via email for users who prefer reduced real-time noise Note: This may be scoped to a follow-on enhancement if it introduces significant complexity. 8. Integration Event Notifications When activity originates from an integration (Zapier, QuickBooks, CompanyCam, etc.), the notification system must accurately attribute the event source and still route the notification through the standard preferences system. Integration-triggered events must not bypass user notification settings. Edge Cases & Exceptions If a user has the Text Messaging add-on disabled, SMS must not appear as an available delivery channel in their notification preferences. If quiet hours are enabled and an event fires during that window, the notification must be held until quiet hours end (or delivered in-app only, depending on channel). The expected behavior for this scenario must be defined during discovery. If a user is deleted or deactivated from an account, their notification preferences must be archived and no further notifications delivered. Notifications triggered by the user's own actions (e.g., a user sending a proposal to themselves for testing) should be suppressed or clearly flagged as self-triggered to avoid confusion. If a notification deep-link points to a record that has since been deleted or archived, the system must handle gracefully without producing an error state. Accounts without the Text Messaging add-on must not see SMS as a notification channel option anywhere in the UI. Mobile push notifications must respect the device-level notification permissions granted by the user in iOS/Android system settings. If permissions are denied at the OS level, the system must surface guidance prompting the user to enable them. Acceptance Criteria [ ] All V1 notification events are preserved and available in V2 with no regression in coverage [ ] Each notification event supports independent per-channel configuration (in-app, email, push, SMS where applicable) [ ] Individual users can configure their own notification preferences without affecting other users on the same account [ ] Account owners and admins can set and manage company-wide default preferences [ ] An in-app notification center is accessible from all pages in the application and displays real-time unread counts [ ] Each in-app notification links directly to the relevant record [ ] Notification history is retained and browsable within the notification center [ ] Read/unread states are tracked and reflected accurately [ ] Users with the Text Messaging add-on inactive cannot select SMS as a notification delivery channel [ ] Quiet hours suppress push and SMS notifications during the defined window [ ] Role-based default preferences are applied to new users at account creation [ ] All notification preference changes take effect immediately without requiring a page reload or re-login [ ] Notifications originating from integrations route through the same preference system as manually triggered notifications Open Questions for Discovery The following questions must be resolved before this ticket moves to active development: Notification history retention window — How long should in-app notifications be retained? 30 days? 90 days? Indefinitely with a manual clear option? Enforcement vs. preference — Which notification types (if any) should account owners be able to enforce so users cannot disable them? Digest / grouping scope — Is notification grouping or digest mode in V2 scope or a follow-on? Quiet hours behavior — When quiet hours suppress a push/SMS notification, should it be delivered after quiet hours end, discarded, or delivered in-app only? Real-time delivery mechanism — This is an architecture decision for the dev team, but PM needs to confirm whether real-time in-app notifications (e.g., bell count updates without page refresh) are in V2 scope. Customer-facing notifications — Should customers receive any notifications through the DripJobs system (e.g., proposal ready, appointment reminder), or is this separate from the internal user notification system? This may overlap with the existing drip/automation and customer portal scope. Mention / @tag system — Is this a V2 feature? If so, notification support for mentions must be coordinated with that ticket. Multi-location / multi-account — If V2 supports multiple locations under a single user login, how do notification preferences map across locations? Dependencies & Related Areas V2 User Roles & Permissions system (role-based defaults depend on this) V2 Text Messaging / SMS add-on architecture V2 Mobile app (push notification infrastructure) V2 Plan Tier architecture (certain notification features may be plan-gated) Customer Portal / Customer-Facing communications (scope boundary must be defined) Drips / Automation system (integration event notifications) Notes This ticket is a placeholder and discovery anchor, not a finalized spec. Scope, priority, and phasing decisions should be made jointly by PM, CTO, and CEO before this moves to development. Individual sub-features identified here may warrant their own child tickets once scoping is complete.
Jeremy harrison 6 days ago
💡 Feature Requests
Planned for V2
V2 Notifications System Overhaul
V1 Notification Settings is a flat, company-level toggle list (New Appointment, Proposal Accepted, Proposal Rejected, Proposal Viewed, Invoice Viewed, Invoice Sent, Chat Message Received) with no channel selection, no per-user preferences, no in-app notification center, and no delivery history. Enhancement Ticket — V2 Notifications System Overhaul Ticket Type: Enhancement Target Version: V2 Status: Placeholder — Pending Discovery & Scoping Priority: TBD Area: Notifications / Settings / User Experience Summary The current V1 notifications system is a flat list of on/off toggles scoped to the company account level. It provides no delivery channel selection, no per-user preference control, no in-app notification inbox, and no notification history. This ticket captures the full scope of known V1 gaps, FeatureBase user requests, and PM roadmap items that should be addressed in the V2 notifications overhaul. This is a placeholder intended to anchor discovery, scope definition, and design decisions before active development begins. User Story As a DripJobs user (owner, admin, or team member), I want a notifications system that gives me meaningful, timely, and personalized alerts about the events that matter to my role, delivered through the channels I prefer, so that I never miss a critical business moment and am not overwhelmed by irrelevant noise. Business Rules (Functional Requirements) 1. Notification Categories & Event Coverage The V2 system must support notifications across all major workflow areas. At minimum, the following event categories must be represented: Proposals & Estimates Proposal sent to customer Proposal viewed by customer Proposal accepted Proposal rejected / declined Proposal expired (if expiration logic exists in V2) Counter-signature completed Appointments & Scheduling New appointment created Appointment confirmed by customer Appointment rescheduled Appointment cancelled Appointment reminder (pre-appointment) Jobs & Work Orders Job created from accepted proposal Work order sent Work order viewed Job status changed Job marked complete Invoices & Payments Invoice sent to customer Invoice viewed by customer Invoice paid Invoice overdue (if applicable) Deposit received Payment failed or declined Communications New chat message received (DJ Chat / in-app messaging) New inbound SMS received (if Text Messaging add-on is active) New inbound email reply received Leads & Pipeline New lead created (manual or via integration) Lead assigned to a team member Deal stage changed Deal archived or lost Team & Internal Task assigned to a user Task completed Mention or tag (if V2 introduces @mentions) New team member added to account Automations (Drips) Drip sequence enrolled Drip step failed to send Drip sequence completed 2. Delivery Channels The system must support multiple notification delivery channels. Each notification event must be configurable per channel independently: In-App (Notification Center) — persistent, visible within the DripJobs app Email — sent to the user's account email address Push Notification — mobile push via iOS and Android apps SMS — optional channel; must only be available if the account has the Text Messaging add-on active 3. Notification Preferences — User-Level Control Each individual user on an account must be able to configure their own notification preferences independently. Company-wide defaults may exist, but individual users must be able to override them for their own account. Preference controls must allow a user to: Enable or disable a notification event entirely Select which delivery channels they want for each event (e.g., in-app only, email + push, etc.) Set quiet hours during which push and SMS notifications are suppressed Account owners and admins must be able to: Set company-wide default notification preferences that apply to new users on the account View which users have notifications enabled for critical events (e.g., invoice paid) Optionally enforce certain notification types so individual users cannot disable them (e.g., payment received) 4. In-App Notification Center V2 must include a persistent in-app notification center (notification inbox/bell) that: Displays a real-time count of unread notifications Shows a chronological feed of all in-app notifications Allows users to mark individual notifications as read or mark all as read Allows users to dismiss or clear notifications Provides a direct link from each notification to the relevant record (proposal, job, invoice, deal, etc.) Persists notification history for a defined lookback window (open question — see below) Distinguishes between read and unread states visually 5. Notification Content & Formatting Each notification must include sufficient context for the user to understand and act without needing to navigate elsewhere first. At minimum, each notification must include: The event type (e.g., "Proposal Accepted") The customer name and/or company name The relevant record name or identifier (e.g., proposal title, job name, invoice number) A timestamp A direct action link to the affected record Notifications must not expose sensitive financial data (e.g., full payment amounts in push/SMS) beyond what is appropriate for the channel. 6. Role-Based Notification Relevance Notification events should be scoped to the user's role where applicable. A field technician should not receive notifications about invoice payment events unless their role warrants it. An admin or owner should receive account-level alerts that a standard user would not. The system must support role-aware defaults while still allowing individual user overrides. 7. Notification Grouping & Digest (Future Consideration) For users who receive high notification volume, the system should support notification grouping or a digest option. For example: Group multiple "Proposal Viewed" events from the same customer into a single notification rather than firing individually Provide a daily or weekly summary digest option via email for users who prefer reduced real-time noise Note: This may be scoped to a follow-on enhancement if it introduces significant complexity. 8. Integration Event Notifications When activity originates from an integration (Zapier, QuickBooks, CompanyCam, etc.), the notification system must accurately attribute the event source and still route the notification through the standard preferences system. Integration-triggered events must not bypass user notification settings. Edge Cases & Exceptions If a user has the Text Messaging add-on disabled, SMS must not appear as an available delivery channel in their notification preferences. If quiet hours are enabled and an event fires during that window, the notification must be held until quiet hours end (or delivered in-app only, depending on channel). The expected behavior for this scenario must be defined during discovery. If a user is deleted or deactivated from an account, their notification preferences must be archived and no further notifications delivered. Notifications triggered by the user's own actions (e.g., a user sending a proposal to themselves for testing) should be suppressed or clearly flagged as self-triggered to avoid confusion. If a notification deep-link points to a record that has since been deleted or archived, the system must handle gracefully without producing an error state. Accounts without the Text Messaging add-on must not see SMS as a notification channel option anywhere in the UI. Mobile push notifications must respect the device-level notification permissions granted by the user in iOS/Android system settings. If permissions are denied at the OS level, the system must surface guidance prompting the user to enable them. Acceptance Criteria [ ] All V1 notification events are preserved and available in V2 with no regression in coverage [ ] Each notification event supports independent per-channel configuration (in-app, email, push, SMS where applicable) [ ] Individual users can configure their own notification preferences without affecting other users on the same account [ ] Account owners and admins can set and manage company-wide default preferences [ ] An in-app notification center is accessible from all pages in the application and displays real-time unread counts [ ] Each in-app notification links directly to the relevant record [ ] Notification history is retained and browsable within the notification center [ ] Read/unread states are tracked and reflected accurately [ ] Users with the Text Messaging add-on inactive cannot select SMS as a notification delivery channel [ ] Quiet hours suppress push and SMS notifications during the defined window [ ] Role-based default preferences are applied to new users at account creation [ ] All notification preference changes take effect immediately without requiring a page reload or re-login [ ] Notifications originating from integrations route through the same preference system as manually triggered notifications Open Questions for Discovery The following questions must be resolved before this ticket moves to active development: Notification history retention window — How long should in-app notifications be retained? 30 days? 90 days? Indefinitely with a manual clear option? Enforcement vs. preference — Which notification types (if any) should account owners be able to enforce so users cannot disable them? Digest / grouping scope — Is notification grouping or digest mode in V2 scope or a follow-on? Quiet hours behavior — When quiet hours suppress a push/SMS notification, should it be delivered after quiet hours end, discarded, or delivered in-app only? Real-time delivery mechanism — This is an architecture decision for the dev team, but PM needs to confirm whether real-time in-app notifications (e.g., bell count updates without page refresh) are in V2 scope. Customer-facing notifications — Should customers receive any notifications through the DripJobs system (e.g., proposal ready, appointment reminder), or is this separate from the internal user notification system? This may overlap with the existing drip/automation and customer portal scope. Mention / @tag system — Is this a V2 feature? If so, notification support for mentions must be coordinated with that ticket. Multi-location / multi-account — If V2 supports multiple locations under a single user login, how do notification preferences map across locations? Dependencies & Related Areas V2 User Roles & Permissions system (role-based defaults depend on this) V2 Text Messaging / SMS add-on architecture V2 Mobile app (push notification infrastructure) V2 Plan Tier architecture (certain notification features may be plan-gated) Customer Portal / Customer-Facing communications (scope boundary must be defined) Drips / Automation system (integration event notifications) Notes This ticket is a placeholder and discovery anchor, not a finalized spec. Scope, priority, and phasing decisions should be made jointly by PM, CTO, and CEO before this moves to development. Individual sub-features identified here may warrant their own child tickets once scoping is complete.
Jeremy harrison 6 days ago
💡 Feature Requests
Planned for V2
Version Control (Proposals/ Invoices)
Consider other access points: Proposal Templates Manual Invoices Custom Sections
Jeremy harrison 11 days ago
💡 Feature Requests
Planned for V2
Version Control (Proposals/ Invoices)
Consider other access points: Proposal Templates Manual Invoices Custom Sections
Jeremy harrison 11 days ago
💡 Feature Requests
Planned
Enable Full Invoice Payment Option When Payment Request is Active
Summary: Add functionality to allow customers to pay the full invoice amount even when a Payment Request is active, which currently limits them to only paying the requested amount. This enhancement will give customers flexibility to pay more than the requested amount (up to the full balance) and will dynamically update payment button calculations including applicable fees. User Story: As a customer receiving an invoice with an active Payment Request, I want the option to pay the full remaining balance instead of being limited to only the requested payment amount, so that I can settle my entire invoice in one transaction if I prefer, rather than making multiple payments.
Jeremy harrison 7 months ago
💡 Feature Requests
Planned
Enable Full Invoice Payment Option When Payment Request is Active
Summary: Add functionality to allow customers to pay the full invoice amount even when a Payment Request is active, which currently limits them to only paying the requested amount. This enhancement will give customers flexibility to pay more than the requested amount (up to the full balance) and will dynamically update payment button calculations including applicable fees. User Story: As a customer receiving an invoice with an active Payment Request, I want the option to pay the full remaining balance instead of being limited to only the requested payment amount, so that I can settle my entire invoice in one transaction if I prefer, rather than making multiple payments.
Jeremy harrison 7 months ago
💡 Feature Requests
Rejected
Payment Follow Ups
We need follow ups when we requested a payment. Can it send a reminder to pay the outstanding balance? Can it keep sending messages until the payment is paid by them? We really need this since we can't manually chase customers who haven't paid.
An Anonymous User 8 months ago
💡 Feature Requests
Rejected
Payment Follow Ups
We need follow ups when we requested a payment. Can it send a reminder to pay the outstanding balance? Can it keep sending messages until the payment is paid by them? We really need this since we can't manually chase customers who haven't paid.
An Anonymous User 8 months ago
💡 Feature Requests
In Progress
Project Management Forecasting Tool
I would like to request a new window that would allow us to project and forecast production based on crew. Set a production goal for a crew of a certain amount of gross income Add up how much is booked for that crew per month in order to see at a glance how much they have booked for the month to better plan and project. Ability to see at a glance the gross amount booked for every crew so that we can project gross revenue for the month as well as see at a glance production booked vs. actual production capacity and plan accordingly based on data. We currently have to manually use an excel spreadsheet in order to do any actual strategizing for production. However, all of the data needed in order to see this information at a glance already exists within this crm. Yet, there is no way to either export it into another software for view or a cability of view. SImply being able to see how much is booked for all crews and per crew on a weekly/monthly basis would be a game changer and save hours and hours. In terms of coding, I personally know it would only require 10-15 hours of coding in order to implement this component into the software… And that’s if I did (who is not a coder). Yet, it would save hours upon hours for all users.
An Anonymous User 8 months ago
💡 Feature Requests
In Progress
Project Management Forecasting Tool
I would like to request a new window that would allow us to project and forecast production based on crew. Set a production goal for a crew of a certain amount of gross income Add up how much is booked for that crew per month in order to see at a glance how much they have booked for the month to better plan and project. Ability to see at a glance the gross amount booked for every crew so that we can project gross revenue for the month as well as see at a glance production booked vs. actual production capacity and plan accordingly based on data. We currently have to manually use an excel spreadsheet in order to do any actual strategizing for production. However, all of the data needed in order to see this information at a glance already exists within this crm. Yet, there is no way to either export it into another software for view or a cability of view. SImply being able to see how much is booked for all crews and per crew on a weekly/monthly basis would be a game changer and save hours and hours. In terms of coding, I personally know it would only require 10-15 hours of coding in order to implement this component into the software… And that’s if I did (who is not a coder). Yet, it would save hours upon hours for all users.
An Anonymous User 8 months ago
💡 Feature Requests
Planned
Add price column to Products/Service page
Please add the option to add columns to the Products/Service page, so we can see each item price.
An Anonymous User 8 months ago
💡 Feature Requests
Planned
Add price column to Products/Service page
Please add the option to add columns to the Products/Service page, so we can see each item price.
An Anonymous User 8 months ago
💡 Feature Requests
On Hold
Social Media Calendar
As a user, have the ability to post pictures/videos/reels of projects, professional advice, tips, etc. to various social media platforms would be extremely useful. It would add another layer of automation to consistently post to social platforms. Considering DribJobs is using AI with other aspects of the application, it should be a seamless addition to help users with caption development, etc. I could elaborate in greater detail but I think the fundamental idea is clear. Thanks in advance!
An Anonymous User 9 months ago
💡 Feature Requests
On Hold
Social Media Calendar
As a user, have the ability to post pictures/videos/reels of projects, professional advice, tips, etc. to various social media platforms would be extremely useful. It would add another layer of automation to consistently post to social platforms. Considering DribJobs is using AI with other aspects of the application, it should be a seamless addition to help users with caption development, etc. I could elaborate in greater detail but I think the fundamental idea is clear. Thanks in advance!
An Anonymous User 9 months ago
💡 Feature Requests
Rejected
Line quantity and price per quantity
Hello, please integrate line quantity and the price per quantity visible on proposals in the customer portal, we price our jobs by the square foot and think this is a very simple option to have to save customers from having to do math themselves and asking us what the price per square foot is. Thank you kindly
An Anonymous User 9 months ago
💡 Feature Requests
Rejected
Line quantity and price per quantity
Hello, please integrate line quantity and the price per quantity visible on proposals in the customer portal, we price our jobs by the square foot and think this is a very simple option to have to save customers from having to do math themselves and asking us what the price per square foot is. Thank you kindly
An Anonymous User 9 months ago
💡 Feature Requests
Planned for V2
Ability to Upload Pictures in Deals
It would be great to have the ability to upload pictures in deals. Right now you have to either upload them in a proposal or in the contact. We regularly have people who are leads send us the “before” photos of their project. This is before we have an appointment with them or sometimes even talk to them. There is not a good way to have these photos easily uploaded or accessible in Drip Jobs. Thank you for your consideration.
An Anonymous User 9 months ago
💡 Feature Requests
Planned for V2
Ability to Upload Pictures in Deals
It would be great to have the ability to upload pictures in deals. Right now you have to either upload them in a proposal or in the contact. We regularly have people who are leads send us the “before” photos of their project. This is before we have an appointment with them or sometimes even talk to them. There is not a good way to have these photos easily uploaded or accessible in Drip Jobs. Thank you for your consideration.
An Anonymous User 9 months ago
💡 Feature Requests
Date format
In my area, date format is dd/mm/yy. The problem is your default format is mm/dd/yy wich causes confusion for my customers when they receive estimate confirmation. Also weird when tracking history of messages or transaction. I would like to have the option to change the format. Even just having it “May 10 2025” would be better
An Anonymous User 9 months ago
💡 Feature Requests
Date format
In my area, date format is dd/mm/yy. The problem is your default format is mm/dd/yy wich causes confusion for my customers when they receive estimate confirmation. Also weird when tracking history of messages or transaction. I would like to have the option to change the format. Even just having it “May 10 2025” would be better
An Anonymous User 9 months ago
💡 Feature Requests
Text receipts
Why is this not a thing? Every other aspect of the process is texted, proposal, invoice, why not receipts? Make it happen
An Anonymous User 9 months ago
💡 Feature Requests
Text receipts
Why is this not a thing? Every other aspect of the process is texted, proposal, invoice, why not receipts? Make it happen
An Anonymous User 9 months ago
💡 Feature Requests
Rejected
Suggestions
I have two suggestions: I’m attaching two screen shots to have the ability to text a clientele that you’re on your way to meet with them and it gives you the ability to select from times. Great communication tool for clients. Another suggestion is a dark screen mode. When I’m on the DripJobs system it’s this big bright white screen. Is there a way currently to set the background to a dark mode or can we implement this feature? Thank you for your consideration. Steve Belvin Floor Warriors
An Anonymous User 9 months ago
💡 Feature Requests
Rejected
Suggestions
I have two suggestions: I’m attaching two screen shots to have the ability to text a clientele that you’re on your way to meet with them and it gives you the ability to select from times. Great communication tool for clients. Another suggestion is a dark screen mode. When I’m on the DripJobs system it’s this big bright white screen. Is there a way currently to set the background to a dark mode or can we implement this feature? Thank you for your consideration. Steve Belvin Floor Warriors
An Anonymous User 9 months ago
💡 Feature Requests
We love the scheduling tool for the Sales & Management teams! We'd love it even more if it had the capability to incorporate production scheduling for the crews. Having the ability for each job lead to manage their own schedule (that's handed down from management) and each crew member having the ability to view theirs and their team's schedule would be amazing!
An Anonymous User 9 months ago
💡 Feature Requests
We love the scheduling tool for the Sales & Management teams! We'd love it even more if it had the capability to incorporate production scheduling for the crews. Having the ability for each job lead to manage their own schedule (that's handed down from management) and each crew member having the ability to view theirs and their team's schedule would be amazing!
An Anonymous User 9 months ago
💡 Feature Requests
Scheduling option for email blasts
Would like to be able to schedule an email blast to be sent on a specified date and time.
An Anonymous User 9 months ago
💡 Feature Requests
Scheduling option for email blasts
Would like to be able to schedule an email blast to be sent on a specified date and time.
An Anonymous User 9 months ago
💡 Feature Requests
Support Staff access to booking form requests
I just found out the only way to have my support staff see the booking form requests coming in is to give them administrator rights. That is a HUGE issue for me and I can see a big mess happening when someone decides to go into settings or templates and mess around. There needs to a user setting for support staff added asap. Thank you!
An Anonymous User 9 months ago
💡 Feature Requests
Support Staff access to booking form requests
I just found out the only way to have my support staff see the booking form requests coming in is to give them administrator rights. That is a HUGE issue for me and I can see a big mess happening when someone decides to go into settings or templates and mess around. There needs to a user setting for support staff added asap. Thank you!
An Anonymous User 9 months ago
💡 Feature Requests
Job Costing should allow spreadsheet downloads
for data input in personal spread sheets we should be able to download job costing metric. This would minimize data input time drastically
An Anonymous User 9 months ago
💡 Feature Requests
Job Costing should allow spreadsheet downloads
for data input in personal spread sheets we should be able to download job costing metric. This would minimize data input time drastically
An Anonymous User 9 months ago
💡 Feature Requests
Being able to upload materials info and cost from home depot and lowes.
we deal with multiple products and materials being able to upload materials cost for our clients to see would be ideal. it makes the sale easier for them to understand and for us to separate materials cost and labor
An Anonymous User 9 months ago
💡 Feature Requests
Being able to upload materials info and cost from home depot and lowes.
we deal with multiple products and materials being able to upload materials cost for our clients to see would be ideal. it makes the sale easier for them to understand and for us to separate materials cost and labor
An Anonymous User 9 months ago
💡 Feature Requests
Default Deposit Setting
All of our proposals, no matter what is being sold, require a 50% deposit to move forward. It would be nice to have a simple default deposit setting encompassing all company proposals without having to either remember every time to add it, or build out a ton of proposal templates to sift through with each individual service.
An Anonymous User 9 months ago
💡 Feature Requests
Default Deposit Setting
All of our proposals, no matter what is being sold, require a 50% deposit to move forward. It would be nice to have a simple default deposit setting encompassing all company proposals without having to either remember every time to add it, or build out a ton of proposal templates to sift through with each individual service.
An Anonymous User 9 months ago
💡 Feature Requests