[Sml] Use case: Calendar availability
Ben Bucksch <ben.bucksch@beonex.com> Thu, 08 February 2024 15:08 UTC
Return-Path: <ben.bucksch@beonex.com>
X-Original-To: sml@ietfa.amsl.com
Delivered-To: sml@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E4F6C1516E0 for <sml@ietfa.amsl.com>; Thu, 8 Feb 2024 07:08:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tYp0VJp1cerp for <sml@ietfa.amsl.com>; Thu, 8 Feb 2024 07:08:54 -0800 (PST)
Received: from mail.server.beonex.com (mail.server.beonex.com [144.76.227.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 271C6C14F61D for <sml@ietf.org>; Thu, 8 Feb 2024 07:08:04 -0800 (PST)
Content-Type: multipart/alternative; boundary="------------fCxkLkN9L38TaXd4XP01feHL"
Message-ID: <806aee50-97a4-4d3f-87c0-3c13988da723@beonex.com>
Date: Thu, 08 Feb 2024 16:07:56 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: fr
References: <a6eaa5b9-76b3-4d9e-ade5-de4f06ef7db8@raffika.com>
From: Ben Bucksch <ben.bucksch@beonex.com>
To: sml@ietf.org
Organization: Beonex
In-Reply-To: <a6eaa5b9-76b3-4d9e-ade5-de4f06ef7db8@raffika.com>
X-Forwarded-Message-Id: <a6eaa5b9-76b3-4d9e-ade5-de4f06ef7db8@raffika.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sml/QnoQb3BuoEl8oIM7hfwUrZgO3TQ>
Subject: [Sml] Use case: Calendar availability
X-BeenThere: sml@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Structured Email <sml.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sml>, <mailto:sml-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sml/>
List-Post: <mailto:sml@ietf.org>
List-Help: <mailto:sml-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sml>, <mailto:sml-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Feb 2024 15:08:59 -0000
Here's a suggestion somebody sent me: Hi Ben, I noticed that, while trying to schedule an appointment ..., it took us 6 days to figure out when we were both free. It was already challenging for him to check messages, and when he was available, I wasn't, and vice versa. I thought, 'how easy it would be if I gave him the opportunity to check my calendar and see my availability directly.' He could schedule an appointment in no time. So, I thought about the possibility of integrating this feature by inserting one's availability (from the calendar we already have) directly into the email we are writing. This way, the recipient just needs to click, see when you are free, figure out a suitable time for him, and respond with the exact day and time. I'm not sure if there's a way to temporarily overlap your calendar with his to easily recognize free slots for both, or something similar. Nevertheless, sending availability [...in] email would significantly shorten the process. E (name redacted)
- [Sml] Use case: Calendar availability Ben Bucksch
- Re: [Sml] Use case: Calendar availability Bogomil Shopov
- Re: [Sml] Use case: Calendar availability Michael Richardson
- Re: [Sml] Use case: Calendar availability Ben Bucksch