Your email connection can break the moment you change your password, and nothing on screen tells you. Proposals and engagement letters keep queuing silently while your client waits.Â
This update closes that gap. FigsFlow now watches your Google and Microsoft connection, flags the failure in Settings, and emails you the list of what stopped sending. Bulk engagement letter creation is faster and more resilient too, and several fixes clean up how the platform handles email delivery, client activity tracking, and subscriptions.
If Your Email Connection Stops Working, You Will Know
A password change or reset is usually what breaks the link between FigsFlow and your Google or Microsoft account. Until now, that failure was invisible. Proposals and engagement letters stopped reaching clients, and nothing in the interface said so.Â
FigsFlow now checks the connection regularly. When it fails, Settings shows a warning explaining that proposals and engagement letters are not reaching clients, with a Reconnect button in place of Disconnect. The follow up email lists the proposals waiting to be sent and copies in the colleagues who created them, so you know exactly what needs resending once you reconnect. A connection that is still working is never flagged by mistake.Â
Drop the Dialling Code on Your Documents
The country list on your proposal and engagement letter footer now includes a “No dialling code” option. Before this, a dialling code was always added to your phone number, and if you had not chosen a country, FigsFlow defaulted to the first one on the list. Numbers already saved with a dialling code are unaffected.Â
Bulk Engagement Letters Are Faster & More Reliable
Proposals covering many entities used to push FigsFlow to generate every document at once. On larger proposals, that was more than the browser could handle, and the generating window could spin indefinitely with no indication anything had gone wrong.Â
Documents are now created in small batches, with the proposal and cover letter generated alongside them instead of waiting in line. The generating window shows the real status of each entity as its document completes, and names the correct entity if one fails. If one document fails, the rest still get created, and a failed save now tells you so instead of leaving you with a draft that lists documents that were never actually generated.
Bug Fixes
Your logo now deletes properly. Removing a logo in Settings, Your Preference, Firm Profile did not previously stick. It reappeared after pressing Update, and again on reload. It is now removed for good, and cannot be deleted by accident while a new image is still uploading.Â
One stuck message no longer blocks the queue. A message that failed to send used to keep retrying and hold up everything queued behind it. Failed messages now retry a set number of times with a pause between attempts, then get set aside so the rest of the queue keeps moving.Â
Client activity now updates on resent, won, and lost emails. Where a proposal was resent, or a won or lost notification was sent, the signatory panel kept showing the client as not engaged, indefinitely. The emails were arriving. FigsFlow was not recording them. It now does.Â
Engagement letters send from your own address again. When an email connection failed, FigsFlow switched it off, and engagement letters then went out from the FigsFlow address instead of the firm’s own, with no notice to anyone. The connection now stays attached to the firm and is simply marked as needing reconnection.Â
Free trials no longer convert to paid plans without your say. Buying AML credits during a free trial saved a card to the account, and FigsFlow read that as a decision to subscribe. The trial could then become a paid plan and get billed automatically at the end of it. A trial now ends unless a plan is actively purchased and stops showing as auto-renewing from day one.Â
Conclusion
Your email connection failing silently was the riskiest gap in this list. It is now caught, flagged, and reported before a client notices a document never arrived. Bulk engagement letter generation and the billing fix close two smaller but real sources of friction.Â
Ask yourself: has a client ever mentioned not receiving a proposal you thought had gone out? Check your Settings for the new connection status now, before it happens again.Â
Â
