Configuring Incoming Email for a basic scenario on a SharePoint 2019 Onpremise

One really neat feature of SharePoint is that you can allow people to send emails to your SharePoint server and have the emails and their attachments be added to a List or a Library. For example, if you have a help desk discussion list, then you could allow users to send their questions as emails to the discussion, where they appear in the SharePoint list along with any attachments.

Here are the following steps to allows Incoming Email on top Sharepoint 2019 :

  1. Add SMTP Feature one of your WFE Sharepoint and set SMTP Service always running

Note : If you are using Windows Server 2022 or having problem MMC error when do setup configuration SMTP, perhaps you can check on this article that i share as well : https://agustox21.wordpress.com/2024/04/23/windows-server-2022-smtp-virtual-server-properties-mmc-detected-an-error-in-a-component-it-is-recommended-to-close-and-restart-mmc/

2. Configure Incoming email on Sharepoint Central Admin

3. Make sure SharePoint Server Publishing Infrastructure at the Site level Actived

After you have set up incoming email handling at the server level, you’ll have to Activate the SharePoint Server Publishing Infrastructure at the Site level.
To do this, browse to your SharePoint site and click the cog at the top right of your browser window so that you can click the option to edit: Site Settings

4. Set Up Your SharePoint List to Accept Emails

Finally, you’ll need to enable receiving emails in the List itself. To do this, browse to the list in your SharePoint site and then click the List tab in the top left tab to get List-related options. Then Click on the List Settings toolbar option (near the far right). Once you are in the List settings page, look for the Communications heading and click the option to manage Incoming e-mail settings. Once in this page, click Yes to the option Allow this list to receive e-mail. If you want to accept attachments, also remember to click the Yes option for Save e-mail attachments
Don’t forget to write down the E-mail address listed here, which should be something like:
YourListName@sharepointdemo.com

5. Configure a connector on the Exchange Server.

  • Create a new send connector on your Exchange Server 2010:
  • Named it, in my scenario, I called “SharePoint Incomings”:
  • Select the “Internal” to the “Select the intended use for this Send connector”:

  • Add tour WFE server FQDN as an SMTP address space:

  • Select the “None”:
  • Add the FQDN of your WFE server as a smart host:

  • Select all your Exchange Servers as the Hub transport:

  • Confirm and click on new:

6. Create a new contact account to each document/list.

Create a new contact in our AD following the sample below (this contact will be used on the document library email settings – see it above):

Kb : https://guidesharepoint.wordpress.com/2015/08/06/configuring-incoming-email-for-a-basic-scenario-on-a-sharepoint-2013-document-library/

Happy Sharepoint-ing

Windows Server 2022 – SMTP Virtual Server – Properties – MMC detected an error in a component, it is recommended to close and restart MMC

When you installing the SMTP Service on Windows Server 2022, i am also not sure why it always error on the MMC and need to be MMC Restarted. Also when you need to add some setting like relay connection, etc and all the setting will not saved and MMC also some error.

I found a good steps, and i already tried and it is works 🙂

  1. Stop SMTPSVC service [Display Name: Simple Mail Transfer Protocol (SMTP)]
  2. Stop IISADMIN service [Display name: IIS Admin Service]
  3. Edit “C:\Windows\System32\inetsrv\MetaBase.xml”
  4. Find: <IIsSmtpServer Location =”/LM/SmtpSvc/1″
  5. Add (Settings are alphabetical): RelayIpList=””
  6. Save file
  7. Start IISAdmin Service
  8. Start SMTPSVC service

Good Good Father

Oh, I’ve heard a thousand stories of what they think You’re like
But I’ve heard the tender whisper of love in the dead of night
And You tell me that You’re pleased, and that I’m never alone

You’re a good, good Father
It’s who You are, it’s who You are, it’s who You are
And I’m loved by You
It’s who I am, it’s who I am, it’s who I am

Oh, and I’ve seen many searchin’ for answers, far and wide
But I’ve known we’re all searchin’ for answers only You provide
‘Cause You know just what we need before we say a word

You’re a good, good Father
It’s who You are, it’s who You are, it’s who You are
And I’m loved by You
It’s who I am, it’s who I am, it’s who I am

Because You are perfect in all of Your ways
You are perfect in all of Your ways
You are perfect in all of Your ways to us
You are perfect in all of Your ways
Oh, You’re perfect in all of Your ways
You are perfect in all of Your ways to us

Oh, it’s love so undeniable
I, I can hardly speak
Peace so unexplainable
I, I can hardly think
As You call me deeper still
As You call me deeper still
As You call me deeper still
Into love, love, love

You’re a good, good Father
It’s who You are, it’s who You are, it’s who You are
And I’m loved by You
It’s who I am, it’s who I am, it’s who I am
You’re a good, good Father
It’s who You are, it’s who You are, it’s who You are
And I’m loved by You
It’s who I am, it’s who I am, it’s who I am

You’re a good, good Father (You are perfect in all of Your ways)
(It’s who You are, it’s who You are, it’s who You are)
(And I’m loved by You) You are perfect in all of Your ways
(It’s who I am, it’s who I am, it’s who I am)
You are perfect in all of Your ways

Youtube : https://www.youtube.com/watch?v=D1WxRWPojtw

Cloud Disaster Recovery Strategies

An effective Disaster Recovery (DR) plan is not just a precaution; it’s a necessity.

The key to any robust DR strategy lies in understanding and setting two pivotal benchmarks: Recovery Time Objective (RTO) and Recovery Point Objective (RPO).

Recovery Time Objective (RTO) refers to the maximum acceptable length of time that your application or network can be offline after a disaster.

Recovery Point Objective (RPO), on the other hand, indicates the maximum acceptable amount of data loss measured in time.

Let’s explore four widely adopted DR strategies:

1. Backup and Restore Strategy:
This method involves regular backups of data and systems to facilitate post-disaster recovery.
– Typical RTO: From several hours to a few days.
– Typical RPO: From a few hours up to the time of the last successful backup.

2. Pilot Light Approach:
Maintains crucial components in a ready-to-activate mode, enabling rapid scaling in response to a disaster.
– Typical RTO: From a few minutes to several hours.
– Typical RPO: Depends on how often data is synchronized.

3. Warm Standby Solution:
Establishes a semi-active environment with current data to reduce recovery time.
– Typical RTO: Generally within a few minutes to hours.
– Typical RPO: Up to the last few minutes or hours.

4. Hot Site / Multi-Site Configuration:
Ensures a fully operational, duplicate environment that runs parallel to the primary system, enabling uninterrupted functionality.
– Typical RTO: Almost immediate, often just a few minutes.
– Typical RPO: Extremely minimal, usually only a few seconds old.

Link : https://www.linkedin.com/feed/update/urn:li:activity:7156103932128251904/

How to Enable Full Accounting In Odoo 17 Community Edition

Odoo is one of the best ERP software available in the market right now. Odoo provides two types of editions, Community and Enterprise. The Odoo community edition is a free basic edition supported by open-source software. Some modules and features are not available in the Odoo community version. But the Enterprise edition Paid, the upgraded version is more suitable for the higher value. Odoo Enterprise Edition is available with unlimited functionality support and full feature. Performance and top speed differentiate between the Enterprise edition and the Community edition.

Many features are not available for the Odoo Community Edition accounting module. Like the dashboard, accounting menu, and chart of account configuration. But these features can be enabled in the community edition version. For this, set up a group for your users in settings. That group comes automatically after installing the invoicing module in Community Edition. Group Name “Show Full Accounting Features.” After setting up your user under the group, you get some features of the accounting module that are not available in the community version

Here are below the following step to enable it :

Step 1: Enable Developer Mode

Step 2: Goto General Settings—>User & Companies—>Groups

Step 3: Select the “Show Full Accounting Features” group

Step 4: Change the application name to Accounting

There are some groups under the Inherited tab. Users added to this group are automatically added to the following groups. You have a few additional tabs to configure menus, views, access rights, and record rules. You can see all the access rights for the group under the Access Rights tab

Step 6: Refresh. You will see the new features added

After enabling the module or browser, you can see the new features added in the invoicing module, like the dashboard, accounting menu, and accounting chart.

Chart Of Account.

Viola, now you already have function to access the COA (Chart Of Account) but this only COA for all report for COA itself you can download on odoo apps store there several vendor give it as free / paid. Or maybe you can create by your self

KONG API Gateway in Docker

Slide Presentation : https://www.slideshare.net/agustox/kongapigatewaypptx

API Gateway vs Load Balance vs Reverse Proxy

What is Kong?

Kong is a scalable, open source API Platform (also known as an API Gateway or API Middleware). Kong was originally built by Kong Inc. (formerly known as Mashape) to secure, manage, and extend over 15,000 Microservices for its API Marketplace, which generates billions of requests per month.

Under active development, Kong is now used in production at hundreds of organizations from startups, to large enterprises and governments including: The New York Times, Expedia, Healthcare.gov, The Guardian, Condè Nast, The University of Auckland, Ferrari, Rakuten, Cisco, SkyScanner, Yahoo! Japan, Giphy and so on.

Kong’s official documentation can be found at docs.konghq.com.

KONG Architecture

Kong Server: This component acts as a proxy for all requests. It consists of a public layer through which all requests for accessing the APIs it exposes are funneled, and a private layer for managing and configuring those APIs. Also, it allows us to enable, disable and configure the installed plugins.

Kong Datastore: an external database where all Kong configurations are stored, along with their plugins or APIs. The datastores supported by default are Cassandra and PostgreSQL. Important: Kong uses its own cache memory to run. However, in certain cases, some plugins such as rate-limiting, require additional components such as Redis

Why Use Kong ?

Kong Ports :

  • 8000 – for proxying. This is where Kong Listens for http traffic
  • 8443 – for proxying https traffic
  • 8001 – provides Kong’s admin API that you can use to operate Kong
  • 7946 – Which Kong uses for inter-nodes communication with other Kong Nodes both UDP dan TCP traffic must be allowed
  • 7373 – used by Kong to communicate with the local clustering agent

Install KONG Community Edition in Docker

1.Install Network for KONG

docker network create kong-net

2. Install Database for Kong (Postgres Version)     

docker run -d --name kong-database --network=kong-net -p 5432:5432 -e "POSTGRES_USER=kong" -e “POSTGRES_DB=kong” -e "POSTGRES_PASSWORD=kong" postgres:9.6

3. Setting Kong Database     

docker run --rm --network=kong-net -e "KONG_DATABASE=postgres" -e "KONG_PG_HOST=kong-database" -e "KONG_PG_PASSWORD=kong" -e "KONG_CASSANDRA_CONTACT_POINTS=kong-database" kong:latest kong migrations bootstrap

4. Then create a kong container and customize the network and db     

docker run -d --name kong --network=kong-net -e "KONG_DATABASE=postgres" -e "KONG_PG_HOST=kong-database" -e "KONG_PG_PASSWORD=kong" -e "KONG_CASSANDRA_CONTACT_POINTS=kong-database" -e "KONG_PROXY_ACCESS_LOG=/dev/stdout" -e "KONG_ADMIN_ACCESS_LOG=/dev/stdout" -e "KONG_PROXY_ERROR_LOG=/dev/stderr" -e "KONG_ADMIN_ERROR_LOG=/dev/stderr" -e "KONG_ADMIN_LISTEN=0.0.0.0:8001, 0.0.0.0:8444 ssl” -p 8000:8000 -p 8443:8443 -p 127.0.0.1:8001:8001 -p 127.0.0.1:8444:8444 kong:latest

5. Test Kong , URL : http://localhost:8001/

Point 1-5 are done, it is meant that Kong API gateway and database already all set-up.

Install Konga (Kong Dashboard) in Docker

  1. Install Konga
docker run -d -p 1337:1337 --network=kong-net --name konga -v /var/data/kongadata:/app/kongadata -e "NODE_ENV=production" pantsel/konga 2. Set up a network for k

2. Set up a network for konga, namely the kong-net network and set up the PostgreSQL db.

docker run --rm --network=kong-net pantsel/konga -c prepare -a postgres -u postgresql://kong:kong@kong-database:5432/konga_db 

3. If successful run the konga and type : http://localhost:1337/

4. Create username and password , then login

5. Goto menu connection and Click button New Connection

6. Type the connection name : kong-net and URL : http://kong:8001 and then Activate

KB :

https://hub.docker.com/_/kong

https://medium.com/telkomdev/berkenalan-dengan-kong-api-gateway-dan-mencobanya-dengan-docker-a4445355493a

https://medium.com/@skzulka/cara-install-kong-konga-di-docker-desktop-windows-6fae9660819a

https://docs.konghq.com/gateway/latest/install/docker/

How to Use IIS SMTP Relay with Connect to Office 365

When you set up a multifunction device or application to send email through Office 365, there are some cases where the device or application can’t connect directly to Office 365. In these cases, you need to set up Internet Information Services (IIS) to work as an intermediary.

You might want to do this in the following scenarios:

  • You don’t have an on-premises messaging system any longer
  • You have line-of-business (LOB) programs or devices in an on-premises environment
  • Your LOB programs and devices have to send email messages to remote domains and to your Exchange Online mailboxes

Here are below the steps :

Step 1: Set up SMTP

First, access the Windows Server Manager interface.

setup smtp

Click the “Add Roles and Features” button. Now you will observe the “before you start”.

setup smtp

Press the Next button. The window asking you to choose an installation type will appear.

setup smtp

Click the Next button after choosing between role-based and feature-based installation. You should now be at the page where you can select your final server.

setup smtp

Click the Next button after selecting a server from the server pool. The Choose server roles screen needs to load.

setup smtp

Click the Next button after selecting the Web Server (IIS) role. The choose features screen must now be visible.

setup smtp

Click the Next button after choosing the SMTP server options. The screen for the web server role must now be visible.

setup smtp

Select the Next option. Now “Select Role Services” is in front of you.

setup smtp

Select the Next option. The screen to verify the installation should appear.

Hit the Install button to begin the setup. You’ll need to give the installation some time to complete. Restarting the server after installation is complete is required.

Step 2: Configure SMTP

  1. Select Start > Administrative Tools > Internet Information Services (IIS) 6.0.
  2. Expand the current server, right-click the SMTP Virtual Server, and then select Properties.
  3. On the General tab, select Advanced > Add.
  4. In the IP Address box, specify the address of the server that’s hosting the SMTP server.
  5. In the Port box, enter 25 and select OK.
  6. On the Access tab, do the following:
    1. Select Authentication and make sure that Anonymous Access is selected.
    2. Select Connection > Only the List Below, and then specify the IP addresses of the devices that will be connecting to the SMTP server, such as printers.
    3. Select Relay > Only the List Below, and then specify the IP address of the devices relaying through this SMTP server
  7. On the Delivery tab, select Outbound Security, and then do the following:
    1. Select Anonymous Authentication.
    2. Enter the credentials of the Office 365 user who you want to use to relay SMTP mail.
    3. Select TLS Encryption.
    4. Select Outbound Connections and in the TCP Port box, enter 25 and select OK.
    5. Select Advanced and specify contoso-com.mail.protection.outlook.com as the Smart Host.

• Replace contoso-com.mail.protection.outlook.com with your own tenants mail exchanger address. You can find this by looking for the MX record of your domain in the admin.microsoft.com portal, located in the Setup section.

Sharepoint Online for Law Firms

Background Story :

Law firms and legal departments keep carrying their banners of heavy document consumers. To follow a paperless business approach, legal professionals invest actively in content and document management solutions. According to Statista, by 2019 legal departments will substantially increase their spending in various document-centric domains. They will invest at least $349 million in contract management (+185% comparing to 2015), $183 million in document management (+44%) and $279 million in matter management (+43%). They will also spend 50% more on collaboration tools and 94% more on legal project management solutions.

Solution:

Here as below the point-point why we choose SharePoint Online to answer what their needed and most common case in Document Management System :

  1. Introduction to SharePoint

Microsoft SharePoint is part of Microsoft 365 (formerly known as Office 365). SharePoint is most commonly referred to as a content management system, as it’s a secure place to store all company documents and content for easy access. It’s also commonly used for creating company intranets.

You can also use SharePoint to create workflows to automate processes within your firm. Some companies use the solution to build apps teams can use to collaborate, share content, and access company info.

To access SharePoint, you and your team can use any browser or the SharePoint app. The mobile app is a great way to access firm information while on the go. SharePoint enables you to create folders (and sub-folders), called Libraries, similar to other file storage tools. This is a great way to organize firm information

SharePoint is a common tool for sharing central folders, files, apps, and information across an organization. It’s a great tool for basic cloud storage.

2. What Is Basic Cloud Storage?

There are effectively 2 types of cloud storage are Basic cloud storage, and Document management systems (DMS).

Basic cloud storage acts like an online filing cabinet, essentially. It’s a place to store and access firm documents and files quickly from anywhere. Other examples of basic cloud storage include Dropbox, OneDrive, and Google Drive.

For some law firms, simple storage isn’t enough. Firms often require features such as version tracking, email management, compliance help, file profiling, and more to truly manage their documents. This is where a DMS comes in.

3. The Difference Between SharePoint and OneDrive

SharePoint and OneDrive are similar, but separate and often used in conjunction with one another as part of an overarching Microsoft 365 Plan. For many law firms:

  • SharePoint holds the firm’s central, shared documents that should be accessible to the entire firm (subject to permissions, of course), and:
  • OneDrive serves as each individual law firm team-members personal/individual storage.

SharePoint includes additional features you won’t find in OneDrive. For example, SharePoint features collaborative documents and offers a shared assets library for your firm. In contrast, OneDrive offers features SharePoint doesn’t, too, such as the ability to comment inside documents.

4. Benefits of SharePoint for Law Firms

SharePoint can deliver several benefits to your law firm. For example, it enables simplified collaboration for your team and is scalable to meet your needs. When used in conjunction with Microsoft 365, it’s the gateway to the other critical tools that make up your tech stack, including OneDrive, Word, PowerPoint, and more.

  • Streamline business processes by offering team members a centralized location for all files, documents, and firm information.
  • Share critical law firm communications to your entire team quickly and efficiently.
  • Enable seamless collaboration for all projects, from in-depth cases to day-to-day work by using SharePoint with other Microsoft 365 tools

5. SharePoint Features

  • Microsoft 365 integration: As part of Microsoft 365, SharePoint integrates seamlessly with your other favorite 365 products. For example, you can share documents from OneDrive or use real-time chat inside SharePoint with Microsoft Teams. Plus, connecting all of your apps is as simple as a few clicks.
  • Enhanced security: Microsoft encrypts your data while at rest and in transit. SSL/TLS connections and 2048-bit keys are used for the encryption of data in transit. At rest, Microsoft uses BitLocker disk-level encryption and per-file encryption. In other words, the data you share inside SharePoint is secure.
  • Real-time collaboration: Your legal team can collaborate on documents and files in real-time, streamlining your work. For example, you and your paralegal can make changes to client documents at the same time.
  • Simplified access to documents and files: Instead of searching through multiple tools for documents and files, your entire team can find everything they need for their work inside SharePoint. Plus, with SharePoint’s customization options, you organize your documents and files in the way that makes the most sense for your firm.
  • Mobile functionality: Your team should have access to important law firm content from anywhere. SharePoint is also available inside a mobile app (for iOS and Android) for on-the-go access. Or, you can access SharePoint via your favorite browser on any laptop or tablet. All you need is the URL for your SharePoint site.

6. Demo

Portal Legal Management Team with custom webpart show the Recent Documents, News, And Also Documents Already Expired that need it to do more actions.

Sample Document libabray that can created multiple folders and customize permission base on Folder.

Sample Demo 2, instead we are using folder to categories the documents. We are created custom metadata like Client, Matter Status, Attorney, Practice Area, and also Expiered Date

And for field Expired data as well we did automation like send an email to spesific email when Matter Status is Closed and etc.

Integration with Matters Library and Power BI for Visualize the Reporting. Nice Rights 🙂

Happy SharePoint-ing,

If your company need me to present this solution you can direct contact me or https://www.infinyscloud.com/

How To Build Unshakeable Customer Trust

English version :

Building customer trust is a complicated process that takes time and patience to achieve. When you get customer trust right, your customers become ambassadors for your brand. In turn, other customers are more likely to purchase your offering based on their recommendations. More consistent customer interactions can only lead to increased sales.

Where to begin?

The foundation of any trust relationship is empathy. This is the ability to recognise and understand the difficulties of your consumers. Your entire organizational policy should centre around the consumer viewpoint. Remember who you are trying to serve. Without customers, there can be no success and, ultimately, no business.

When building strategies and hiring new employees, be sure to select people that are empathic to the customers’ point of view. People that can consider the situation from both sides are key in building trust and bridging the gap between customers and organizations.

Practicing Empathy

Understanding the experiences of others can be a challenge. How do we put ourselves in the shoes of people, that have lived experiences vastly different from our own? Sometimes it best to take a practical and hands on approach. Take Barclays bank for example. They have been training their employees with an age simulation suit (weighted with decreased visibility) to provide the experience of someone with vision problems and mobility issues trying to access their services. These suits are even capable of inducing temporary joint pain!

Building the experience of your organization around the people that struggle most to engage is a genuine and fulfilling way to build trust with those customers. The elderly and disabled people should be treated as equally entitled to access your products or services without having to face unnecessary barriers like poor access.

Training in empathy and awareness is far from straightforward. How can you simulate the pain sometimes experienced by elderly and disabled people? But If you make the effort to do the most for all of your customers, not just the ones that are easy to serve, the returns in customer loyalty and trust can be enormous.

The right thing at the right time

Organizations flouting customer trust has become an ever more common occurrence. Worse still are organizations that only act with decency and morality when it suits them. Consumers often forget how much power they hold over the organizations and institutions that serve them.

Activism can be polarising. That is why understanding your organization’s core values and purpose is so important. Embracing causes or any of the fights for social justice must be woven into the very fabric of what you do, not paid lip service to for moral clout.

Fashion outlet BooHoo is an example of getting it wrong in terms of building customer trust. In the wake of the BLM movement on social media, the company committed to support more diversity and inclusion. At the same time, they were linked to illegal sweat shops in the background.

One of the biggest metrics for customer engagement is the extent to which customers trust the organization to do the right thing. That is not to say you must take up the torch for every cause, that is not always possible. But you can design your strategies around the issues that represent your values and organizational goals. If you are a coffee company, you might commit to sustainable and fair-trade products. If you are a clothing company, you might commit to reducing fasting fashion and ban slave labour practices.

Tell the Truth

Customers and service users are not fools. They will be able to tell the authentic from those that are not. If your organization makes a mistake, be honest with your customers about it. Trust is built through cycles of trial and error, growth and expansion.

Too often toxic company culture prevents people from owning their mistakes, by overly punishing a single mistake, rather than the consistency or frequency with which mistakes occur. One mistake is not a problem, it is a learning experience.

When you come down hard on a first-time mistake, it doesn’t correct the offending behaviour, it only teaches more subversive behaviours. When there is no room for growth, employees are less willing to step into the line of fire and have a growth moment.

And it is always the customers that pay for these learned behaviours. If your employees are so fearful of making a mistake they pass the blame onto the customer, trust will be permanently damaged.

Building a better future

Customer trust is a tricky subject. It requires understanding, empathy, and honesty.

Indonesia Version:

Membangun kepercayaan pelanggan adalah proses rumit yang membutuhkan waktu dan kesabaran untuk mencapainya. Ketika Anda mendapatkan kepercayaan pelanggan dengan benar, pelanggan Anda menjadi duta untuk merek Anda. Pada gilirannya, pelanggan lain akan cenderung membeli produk Anda berdasarkan rekomendasi mereka. Interaksi pelanggan yang lebih konsisten hanya dapat meningkatkan penjualan.

Dari mana memulainya?

Dasar dari setiap hubungan kepercayaan adalah empati. Ini adalah kemampuan untuk mengenali dan memahami kesulitan konsumen Anda. Seluruh kebijakan organisasi Anda harus berpusat pada sudut pandang konsumen. Ingatlah siapa yang ingin Anda layani. Tanpa pelanggan, tidak akan ada kesuksesan dan pada akhirnya tidak ada bisnis.

Ketika membangun strategi dan merekrut karyawan baru, pastikan untuk memilih orang-orang yang berempati terhadap sudut pandang pelanggan. Orang-orang yang dapat mempertimbangkan situasi dari kedua sisi adalah kunci dalam membangun kepercayaan dan menjembatani kesenjangan antara pelanggan dan organisasi.

Mempraktikkan Empati

Memahami pengalaman orang lain bisa menjadi sebuah tantangan. Bagaimana kita menempatkan diri kita pada posisi orang lain, yang memiliki pengalaman hidup yang sangat berbeda dengan pengalaman kita sendiri? Terkadang yang terbaik adalah dengan melakukan pendekatan yang praktis dan langsung. Ambil contoh bank Barclays. Mereka telah melatih karyawan mereka dengan pakaian simulasi usia (yang dibebani dengan penurunan visibilitas) untuk memberikan pengalaman kepada seseorang dengan masalah penglihatan dan masalah mobilitas yang mencoba mengakses layanan mereka. Pakaian ini bahkan mampu menimbulkan nyeri sendi sementara!

Membangun pengalaman organisasi Anda di sekitar orang-orang yang paling sulit untuk dilibatkan adalah cara yang tulus dan memuaskan untuk membangun kepercayaan dengan para pelanggan. Para lansia dan penyandang disabilitas harus diperlakukan sama berhak untuk mengakses produk atau layanan Anda tanpa harus menghadapi hambatan yang tidak perlu seperti akses yang buruk.

Melatih empati dan kesadaran bukanlah hal yang mudah. Bagaimana Anda dapat mensimulasikan rasa sakit yang terkadang dialami oleh para lansia dan penyandang disabilitas? Namun, jika Anda berusaha melakukan yang terbaik untuk semua pelanggan Anda, bukan hanya pelanggan yang mudah dilayani, hasil yang didapat dari kesetiaan dan kepercayaan pelanggan bisa sangat besar.

Hal yang tepat pada waktu yang tepat

Organisasi yang mengabaikan kepercayaan pelanggan telah menjadi hal yang semakin sering terjadi. Lebih buruk lagi adalah organisasi yang hanya bertindak dengan kesopanan dan moralitas ketika itu sesuai dengan mereka. Konsumen sering kali lupa seberapa besar kekuatan yang mereka miliki atas organisasi dan institusi yang melayani mereka.

Aktivisme dapat menjadi polarisasi. Itulah mengapa memahami nilai-nilai inti dan tujuan organisasi Anda sangat penting. Merangkul tujuan atau memperjuangkan keadilan sosial haruslah terjalin ke dalam struktur dari apa yang Anda lakukan, bukan hanya sekedar basa-basi demi pengaruh moral.

Gerai fesyen BooHoo adalah contoh kesalahan dalam membangun kepercayaan pelanggan. Setelah gerakan BLM di media sosial, perusahaan ini berkomitmen untuk mendukung lebih banyak keragaman dan inklusi. Pada saat yang sama, mereka juga dikaitkan dengan toko-toko keringat ilegal di belakangnya.

Salah satu metrik terbesar untuk keterlibatan pelanggan adalah sejauh mana pelanggan mempercayai organisasi untuk melakukan hal yang benar. Ini bukan berarti Anda harus mengambil obor untuk setiap masalah, hal itu tidak selalu memungkinkan. Tetapi Anda dapat merancang strategi Anda di sekitar isu-isu yang mewakili nilai-nilai dan tujuan organisasi Anda. Jika Anda adalah perusahaan kopi, Anda dapat berkomitmen pada produk yang berkelanjutan dan perdagangan yang adil. Jika Anda adalah perusahaan pakaian, Anda dapat berkomitmen untuk mengurangi mode cepat saji dan melarang praktik perbudakan.

Katakan yang Sebenarnya

Pelanggan dan pengguna layanan bukanlah orang bodoh. Mereka akan dapat membedakan mana yang asli dan mana yang tidak. Jika organisasi Anda melakukan kesalahan, jujurlah kepada pelanggan tentang hal itu. Kepercayaan dibangun melalui siklus coba-coba, pertumbuhan dan ekspansi.

Terlalu sering budaya perusahaan yang beracun mencegah orang untuk mengakui kesalahan mereka, dengan menghukum satu kesalahan secara berlebihan, daripada konsistensi atau frekuensi terjadinya kesalahan. Satu kesalahan bukanlah masalah, melainkan sebuah pengalaman belajar.

Ketika Anda menghukum dengan keras pada kesalahan pertama kali, hal itu tidak akan memperbaiki perilaku yang menyinggung, melainkan hanya mengajarkan perilaku yang lebih subversif. Ketika tidak ada ruang untuk berkembang, karyawan kurang bersedia untuk melangkah ke dalam garis tembak dan memiliki momen pertumbuhan.

Dan pelangganlah yang selalu membayar untuk perilaku yang dipelajari ini. Jika karyawan Anda begitu takut melakukan kesalahan sehingga mereka melimpahkan kesalahan kepada pelanggan, kepercayaan akan rusak secara permanen.

Membangun masa depan yang lebih baik

Kepercayaan pelanggan adalah subjek yang rumit. Hal ini membutuhkan pemahaman, empati, dan kejujuran.

Original Source : http://www.servicebrandglobal.com/howtobuildunshakeablecustomertrust/

5 Steps OF Cloud Migration Strategies

A. What are the Main Benefits of Migrating to the Cloud?

Here are some of the benefits that compel organizations to migrate resources to the public cloud:

  • Scalability
    Cloud computing can scale to support larger workloads and more users, much more easily than on-premises infrastructure. In traditional IT environments, companies had to purchase and set up physical servers, software licenses, storage and network equipment to scale up business services.
  • Cost
    Cloud providers offer managed services that lower your operational overhead and simplify maintenance tasks such as upgrades. Companies migrating to the cloud can spend significantly less on IT operations. They can devote more resources to innovation—developing new products or improving existing products.
  • Performance
    Migrating to the cloud can improve performance and end-user experience. Applications and websites hosted in the cloud can easily scale to serve more users or higher throughput, and can run in geographical locations near to end-users, to reduce network latency.
  • Digital experience
    Users can access cloud services and data from anywhere, whether they are employees or customers. This contributes to digital transformation, enables an improved experience for customers, and provides employees with modern, flexible tools.

B. What are Common Cloud Migration Challenges?

Cloud migrations can be complex and risky. Here are some of the major challenges facing many organizations as they transition resources to the cloud.

Lack of Strategy

Many organizations start migrating to the cloud without devoting sufficient time and attention to their strategy. Successful cloud adoption and implementation requires rigorous end-to-end cloud migration planning. Each application and dataset may have different requirements and considerations, and may require a different approach to cloud migration. The organization must have a clear business case for each workload it migrates to the cloud.

Cost Management

When migrating to the cloud, many organizations have not set clear KPIs to understand what they plan to spend or save after migration. This makes it difficult to understand if migration was successful, from an economic point of view. In addition, cloud environments are dynamic and costs can change rapidly as new services are adopted and application usage grows.

Vendor Lock-In

Vendor lock-in is a common problem for adopters of cloud technology. Cloud providers offer a large variety of services, but many of them cannot be extended to other cloud platforms. Migrating workloads from one cloud to another is a lengthy and costly process. Many organizations start using cloud services, and later find it difficult to switch providers if the current provider doesn’t suit their requirements.

Data Security and Compliance

One of the major obstacles to cloud migration is data security and compliance. Cloud services use a shared responsibility model, where they take responsibility for securing the infrastructure, and the customer is responsible for securing data and workloads. 

So while the cloud provider may provide robust security measures, it is your organization’s responsibility to configure them correctly and ensure that all services and applications have the appropriate security controls. 

The migration process itself presents security risks. Transferring large volumes of data, which may be sensitive, and configuring access controls for applications across different environments, creates significant exposure.

C. Cloud Migration Strategies

Gartner has identified five cloud migration techniques, known as the “5 Rs”. Organizations looking to migrate to the cloud should consider which migration strategy best answers their needs. The following is a brief description of each:

  • Rehost. Rehosting, or ‘lift and shift,’ involves using infrastructure-as-a-service (IaaS). You simply redeploy your existing data and applications on the cloud server. This is easy to do and is thus suited for organizations less familiar with cloud environments. It is also a good option for cases where it is difficult to modify the code, and you want to migrate your applications intact. 
  • Refactor. Refactoring, or ‘lift, tinker, and shift,’ is when you tweak and optimize your applications for the cloud. In this case, a platform-as-a-service (PaaS) model is employed. The core architecture of the applications remain unchanged, but adjustments are made to enable the better use of cloud-based tools.
  • Revise. Revising builds upon the previous strategies, requiring more significant changes to the architecture and code of the systems being moved to the cloud. This is done to enable applications to take full advantage of the services available in the cloud, which may require introducing major code changes. This strategy requires foreplanning and advanced knowledge. 
  • Rebuild. Rebuilding takes the Revise approach even further by discarding the existing code base and replacing it with a new one. This process takes a lot of time and is only considered when companies decide that their existing solutions don’t meet current business needs. 
  • Replace. Replacing is another solution to the challenges that inform the Rebuild approach. The difference here is that the company doesn’t redevelop its own native application from scratch. This involves migrating to a third-party, prebuilt application provided by the vendor. The only thing that you migrate from your existing application is the data, while everything else about the system is new.