<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Crm on Ergophobia</title><link>https://ergophobia.org/tags/crm/</link><description>Recent content in Crm on Ergophobia</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 07 Sep 2026 00:00:00 -0400</lastBuildDate><atom:link href="https://ergophobia.org/tags/crm/index.xml" rel="self" type="application/rss+xml"/><item><title>spanish-academy — week of 2026-08-31</title><link>https://ergophobia.org/updates/2026-09-07-spanish-academy/</link><pubDate>Mon, 07 Sep 2026 00:00:00 -0400</pubDate><guid>https://ergophobia.org/updates/2026-09-07-spanish-academy/</guid><description>&lt;p&gt;Three fixes, all landed Sunday night.&lt;/p&gt;&#10;&lt;p&gt;The one that matters most is on the lead side. Of the several paths that create&#10;a lead in the CRM, the placement flow was the only one setting a follow-up&#10;status. Everything else, the web forms and the assistant&amp;rsquo;s handoff, was dropping&#10;leads in with no status at all. That meant nobody could tell from the CRM what&#10;had been contacted and what hadn&amp;rsquo;t. Every path now stamps the same default&#10;status, and the value lives in one place because the CRM rejects the whole&#10;record on a typo, and I&amp;rsquo;d rather not lose a lead over one.&lt;/p&gt;</description></item></channel></rss>