Insights

Ideas to build and operate better.

Guides, analysis and lessons on product, artificial intelligence, growth, communications and cloud.

Editorial themes

Software and SaaS development

Digital products that solve, scale and evolve.

AI, automation and data

AI systems for real-world processes.

Marketing, ecommerce and marketplaces

Demand, catalogue, partners and conversion.

Communications and customer care

Every conversation in the right channel.

Cloud, infrastructure and operations

Available, observable and ready services.

results

3 results

Diagram showing a message move from the primary channel to an alternative after delivery status and permissions are checked.

Comunicaciones y atención al cliente6 min

Communication Channel Fallback: When to Switch Channels Without Duplicating Messages

Design fallback rules that distinguish temporary from permanent errors, respect preferences and permissions, and prevent duplicate messages when switching channels.

↗

Customer profiles from multiple systems being compared before a decision to merge them or send them for review.

Inteligencia artificial, automatización y datos6 min

Duplicate Customers Across Systems: When to Merge Records and When to Request a Review

Set rules for detecting duplicate customers, deciding which records to merge, and protecting useful data through confidence levels, human review, and traceability.

↗

Conceptual diagram of an integration event with included data, references, and connected systems.

Integraciones, APIs y sistemas conectados8 min

How to Decide Which Data to Include in an Integration Event

A practical framework for deciding which data travels in an event, which data is retrieved later, and how to avoid dependencies, stale data, and security risks.

↗