<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Coevera Blueprints</title>
    <link>https://coevera.webplanet.sk/</link>
    <atom:link href="https://coevera.webplanet.sk/feed.xml" rel="self" type="application/rss+xml"/>
    <description>Implementation blueprints for Coevera CRM (formerly Pipeliner). Each one starts from a business problem and documents the working configuration end to end — data model, fields, automation, limits and verification.</description>
    <language>en</language>
    <lastBuildDate>Tue, 02 Sep 2026 00:00:00 +0000</lastBuildDate>
    <item>
      <title>How do you get AI to read a document and fill in CRM fields reliably?</title>
      <link>https://coevera.webplanet.sk/blueprints/ai-fields-read-documents.html</link>
      <guid isPermaLink="true">https://coevera.webplanet.sk/blueprints/ai-fields-read-documents.html</guid>
      <pubDate>Tue, 02 Sep 2026 09:00:00 +0000</pubDate>
      <category>AI fields</category>
      <description>Blueprint 002. Recognise once, read many — one AI field reads the attached documents and writes a JSON worksheet; every other field is a cheap text reader. Covers supported field types, why every AI-to-AI dependency must be its own process, asynchronous completion triggers, and the failure modes that report success while writing nothing.</description>
    </item>
    <item>
      <title>How do you run five different kinds of customer request through one help desk?</title>
      <link>https://coevera.webplanet.sk/blueprints/one-entity-five-request-types.html</link>
      <guid isPermaLink="true">https://coevera.webplanet.sk/blueprints/one-entity-five-request-types.html</guid>
      <pubDate>Tue, 02 Sep 2026 00:00:00 +0000</pubDate>
      <category>Data model</category>
      <description>Blueprint 001. One custom entity, five CustomEntityType sub-types, the native typeId as discriminator — one queue and one reference-number series carrying five different field sets. Covers why a custom type dropdown cannot work, why five separate entities also fail, the auto-default sub-type trap, and the proxy-Quote pattern required because approval processes cannot target a custom entity.</description>
    </item>
  </channel>
</rss>
