I watched Marc's recent appearance on CNBC with great interest where he addressed the market's near-term volatility (YouTube link).

This is precisely the buyer experience iDialogue enables, the ability to generate multi-quotes from a single opportunity and give the buyer a rich, personalized experience to review their options and quickly commit to a long-term contract.

"A great Buyer Experience starts with a great Employee Experience."

​From a Salesforce opportunity, a Sales Rep can quickly configure a multi-quote room with options for 1, 2, or 3 year contracts.

A personalized quote room link is shared with the buyer (via iDialogue enhanced quote emails) where the buyer can review contract options, pricing calculators, and product brochures.

For any CEOs, Revenue Ops, or Sales Executives looking for a pre-built playbook for long-term contracts, please feel free to contact me anytime mike@idialogue.app.

A headless content management system, or sometimes called an "API First" CMS, decouples the front end clients, aka “heads”, from the backend “body”.

This is in contrast to Web 1.0 content management systems that were more monolithic and primarily evolved from desktop website content only.

Examples of how this technical architecture delivers business value:

• Enables Marketers to centrally manage content in one location, and publish content to multiple form factors
• Defining content using responsive design patterns encourages more content reuse
• Aligns mobile and desktop application development efforts around common user identity, authentication, data models, and content
• Faster time to market and delivery
• Fewer content deployment errors

​

The iDialogue API is an example of a headless CMS that primarily uses Salesforce as the backend, plus connects with other  best-of-breed web services.

Example of front-end apps using the iDialogue API:

• iDialogue public "rooms" are developed using React
• Lightning components
• iPhone and Android native mobile applications
• Mobile browser experiences
• Salesforce Flow Actions

All of the above front ends are centrally supported through a single API.
The iDialogue API also proxies access to various back ends:

• Salesforce: System of record for Contact/User identity and customer data model
• Stripe Payments
• Twilio SMS and Text messaging
• Adobe and Microsoft document conversion services

iDialogue broadly defines "content" as any customer-facing digital asset, including:

• HTML web pages and images
  
• Raw text
• PDF and Word documents (either dynamically created or static)
• JSON representations of data
• Interactive applications, SPAs, and Javascript