SML: Difference between revisions

Line 2:

SML (Structured Email) is a standard for adding machine-readable data to email messages.

It enables developers to create more intelligent email applications that can understand and act on the content of messages, rather than just treating them as plain text.

It enables developers to create more intelligent email applications that can understand and act on the content of messages, rather than just treating them as plain text. There are infinite use cases in which gathering information from email and re-using them can be useful. Help us to find them all.

What is currently done via email, but manually? How can we automate it?

Line 18:

* Invoice, order confirmation sent to accounting application puts products and price in a database of pitched products

* Delivery notification when linked to order and/or invoice by ID, can show overall status of each ordered product , including order, delivery status, dates, price, etc currently scattered in at least 4 emails.

* Order Management: When receiving an meeting invitation, seeing whether you already have appointments can show overall status of each ordered product, including order, delivery status, expected delivery time, dates, price, vendor information, custom notes, etc. Currently, this information is scattered in at least 4 emails, or even more when orders are split or merged during delivery.

~~<nowiki>~~*~~</nowiki>~~ Order Management: When receiving an meeting invitation, seeing whether you already have appointments can show overall status of each ordered product, including order, delivery status, expected delivery time, dates, price, vendor information, custom notes, etc. Currently, this information is scattered in at least 4 emails, or even more when orders are split or merged during delivery.

* Repairs: Guarantee. Terms. Call service technician.