Customer Requests

Currently, when leads are uploaded, the system will reorganize the phone numbers in numerical order. Having the option to allow the numbers uploaded as they are presented on the upload sheet would be helpful to the organization and prioritization of outreach.

Hi LeadSimple team, I'm John Ely, owner-operator at Rely Real Estate Co. We've integrated your REST API into our analytics layer to surface "last contact" data on tenant communications — it's been a real value-add for our delinquency workflow. I'd like to ask whether you have plans (or an undocumented option) to support server-side date filtering on two endpoints: GET /rest/text_messages GET /rest/calls What we'd like to be able to do: Filter records by created_at so we can pull only recent communications (e.g., last 90 days) rather than the full account history. Something like: GET /rest/text_messages?created_at_gte=2026-02-12&per_page=100 A working sort=-created_at parameter would also solve this — we could paginate newest-first and stop once we hit our cutoff. Why it matters for us: We currently have ~26,000 text messages and ~6,000 calls in our account. To pull a 90-day window of either, we have to paginate every record (260+ pages of texts) and filter client-side, since the only supported parameters appear to be page and per_page. That puts heavy load on your rate limits — we routinely hit the records budget and pause through 65-second retry windows. Our refresh job runs once nightly at 2 AM MT (mapped to the 3x rate scaling window per your docs), and even then a single text_messages pull takes 15–20 minutes. What we've tried: sort=-created_at — confirmed silently ignored in testing created_at_gte, created_at_from, since, from, filter[created_at_gte] — all 504 timeouts or no effect Reducing lookback window — only partial mitigation since we still paginate the older records first My ask: Three options, ranked by what would help us most: Server-side date filter on /text_messages and /calls (created_at_gte or similar). Biggest win. Working sort parameter so we can paginate newest-first and stop at our cutoff. If neither is on the roadmap: point me toward any existing pattern I've missed — maybe an undocumented filter, a different endpoint that returns the same data with filter support, or a webhook that pushes new communications so we can avoid the full re-pull. Even just a "no, not planned, here's our suggested workaround" response would be helpful — it lets us decide whether to invest in further optimization or move to a webhook-based ingestion model. Happy to provide our account ID or API key ID if that helps your engineering team trace specific request patterns. Thanks for the consideration — John Ely Owner, Rely Real Estate Co. john@relyrealestateco.com

The recent removal of task checkboxes should not be a forced system-wide change with no flexibility. What may improve workflow accuracy for one company can significantly slow down or disrupt workflows for another. Please change it back or add an admin-controlled toggle that allows companies to: Enable or disable manual task completion checkboxes Choose whether tasks must be completed through execution/skipping only Customize task behavior based on operational preference Right now, the system feels more arbitrarily constrained instead of more dynamic. Teams relied on the checkbox functionality for speed, organization, and workflow management, especially in high-volume operational environments. The better approach is configurability, not forced standardization. LeadSimple’s strength has always been flexibility and workflow customization. Changes like this should be optional settings controlled at the admin level, not universal UX decisions imposed on all users regardless of operational style. Please bring flexibility back into the platform. Stop ruining this system.

Please bring back the check offs for emails and texts. We send the emails through another system for documentation and are being forced to skip each of these tasks now. Sometimes I've already communicated things inside the email template and want to document that this is completed, not skipped.

Please bring back the check offs for emails and texts. We send texts/emails through other systems for documentation/functionality and are being forced to skip each of these tasks now. Commonly we've already communicated things inside the email template and want to document that this is completed, not skipped.

The new dark mode looks great, it just has some contrast issues when tagging people, its really straining on the eyes since the text is white and the tag coloring is a bright yellow, please change it for dark mode

It would be great to mark unknown callers (answered) quickly as spam from the tasks menu. A button would allow them to be added to the blocked list without having to go through the settings menu. It would also clear the task all in one swoop, saving several steps.

It would be nice if we could "Reply All" when emailing.

I'd love to have a default time for tasks due across the account. Like, always set it to 5pm and only adjust it if there is a process due date that is "5 minutes after" or something like that. It could obviously be adjusted but then if it was due 1 day later, it would just be due by 5pm on the next day, not exactly 24 hours later. Or if a stand alone task is created, it would default to being due at the global default and then could be adjusted as needed.